Fix matching multiple OData routing metadata - #1587
Open
lpperras wants to merge 1 commit into
Open
Conversation
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Author
|
@microsoft-github-policy-service agree |
Author
|
@xuzhg @WanjohiSammy we might need to shift our versioning strategy for our product depending on if this will ever be approved. We don't want to run of a fork but need this fix to move forward. Could you please let me know if there is not chance this makes it to the product so that we can align accordingly on our side? |
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.
Fixes #753.
ODataRoutingMatcherPolicypreviously considered only the firstIODataRoutingMetadataentry attached to an endpoint.The matcher now evaluates metadata entries in order and uses the first
successful translation, including its EDM model, route prefix, and updated
route values.
Added focused unit coverage for:
The implementation approach is based on the solution proposed by
@commonsensesoftware in the original issue.