feat!: use simplified bound action paths by default#142
Closed
Conversation
Member
Author
|
@chgeo This would mean that clients and users relying on action paths that are prefixed with namespaces would need to update or use the flag (see cds-dk PR). |
chgeo
reviewed
Mar 2, 2026
Member
chgeo
left a comment
There was a problem hiding this comment.
I also wondered if this change of paths would be breaking.
An alternative would to be make it an opt-in flag, right?
So maybe you should ask back why for the issue reporter these shorter paths are such a big think, and whether they'd be fine with opting-in.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Bound action paths now use simplified names by default (e.g.,
/Products({ID})/Discountinstead of/Products({ID})/ODataDemo.Discount). The new--openapi:fqActionPathsCLI flag allows to restore fully qualified names if needed.