fix: use OData V4 path for OpenAPI server URL if no protocol is set to match @sap/cds default behavior - #175
Open
cronossclk wants to merge 2 commits into
Open
Conversation
added 2 commits
August 20, 2026 16:42
…o match @sap/cds default behavior Signed-off-by: Lukas Schwabe <lukas.schwabe@amag.ch>
Contributor
|
Hi @cronossclk , thank you for reporting this behaviour and for providing a fix! I thus propose the following addition to your PR:
Users can then restore the old behaviour by providing Best, |
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.
Before: When OpenAPI generates a document for an OData V4 service, it may advertise the REST base path:
After: The generated
servers.urlmatches the service’s OData V4 runtime endpoint:This affects only the URL advertised in the OpenAPI document. It does not change:
@path--openapi:urlvaluesThis PR fixes #174
Test results: