Feature/endpoint path paratemer - #12
Open
matusmacik wants to merge 2 commits into
Open
Conversation
As defined in #11289, added support for path parameter. Implemented for single object endpoint builder. Also added tests for update behaviour.
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
1 participant
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.
Summary
Implements support for flexible path parameter resolution in endpoint URLs, addressing scenarios where the target application uses different path parameter names than those defined in the connector schema (see WP#11289).
Details
pathParameter("attribute", "username") :
Uses an extractor to resolve the value of "username" and maps it to the path parameter "attribute".
pathParameter("attribute") :
Implicitly uses the UID value as the path parameter for "attribute".
No explicit path parameter defined:
Extracts the parameter name from the endpoint path, verifies it against the schema, and if it corresponds to the UID, uses the UID value automatically.