Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Warnings node_modules/@cap-js/change-tracking/index.cds:23:3: No OData navigation property generated, target “sap.changelog.ChangeLog” is outside of service ... #121

Open
D027152 opened this issue Sep 18, 2024 · 2 comments

Comments

@D027152
Copy link

D027152 commented Sep 18, 2024

Hello

Some services that we have defined in our repository https://github.tools.sap/erp4sme/crypto-for-business contain entities that are enabled for change tracking via annotation @changelog.
For all these services the command cds build --production creates warnings like the following:
[WARNING] node_modules/@cap-js/change-tracking/index.cds:23:3: No OData navigation property generated, target “sap.changelog.ChangeLog” is outside of service ...:
image

These warnings seem not to harm. However: Is there a possibility to get rid of them?

The reason for the warnings seems to be that each entity gets the annotation changes, which points to entity ChangeView, which contains the association changeLog pointing to entity ChangeLog. The entity ChangeView is contained in our odata services, but entity ChangeLog is not.

to reconstruct:

@D027152
Copy link
Author

D027152 commented Nov 22, 2024

Hello

This issue still exists. Is there any recommendation for this?

Thank you,
Stefan

@nkaputnik
Copy link
Contributor

Hello @D027152
these warnings indeed do no harm, but I unfortunately don't know how to get rid of them, except working around this by manually creating a service entity proxy in your servic definition and using redirects, but I would say this solution is high effort and quite ugly compared to living with the warnings.

I'll take this into our regular modeling-sync to discuss this with the compiler experts, but this may take some time.

Best,
Nick

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants