Repository navigation
fix(core-internal): support RFC 6570 prefix modifiers in UriTemplate (#3000) #3003
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
Open
MokuLakshithReddy
wants to merge
3
commits into
modelcontextprotocol:main
Choose a base branch
from
MokuLakshithReddy:fix/uri-template-prefix-modifiers
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+242
−41
Open
Changes from all commits
Commits
Show all changes
3 commits
Select commit
Hold shift + click to select a range
f30efc5
fix(core-internal): support RFC 6570 prefix modifiers in UriTemplate …
MokuLakshithReddy 2e8e0c9
fix(core-internal): enforce RFC 6570 prefix max-length and modifier m…
MokuLakshithReddy 7f1ca4c
fix(core-internal): encode multi-variable values and join with operat…
MokuLakshithReddy File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,5 @@ | ||
| --- | ||
| '@modelcontextprotocol/core-internal': patch | ||
| --- | ||
|
|
||
| Support RFC 6570 prefix modifiers (`:N`) in `UriTemplate`: retain clean variable names in `variableNames` and `match()`, and apply prefix truncation to Unicode code points before percent-encoding during expansion. |
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
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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
match()doesn't use the prefix at all, so/users/{id:3}matches/users/abcdefand returnsid: 'abcdef', a URI this template could never expand to. Is that intended (prefix only affects expansion), or should the pattern be bounded forprefixvars? Either way a test pinning the behavior might help, since resource templates usematch()to route reads.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Prefix modifiers in RFC 6570 define variable expansion truncation. Matching in this SDK extracts the segment value without lossy truncation. I have added an explicit regression test to pin this contract (
/users/{id:3}extracts{ id: "abc" }and{ id: "abcdef" }).