Handle validation for Composite URIs without parens#2004
Merged
Conversation
Parentheses are optional when creating composite and nested URIs so this updates the validation to handle missing parens as well. Follow on to apache#1847
mattrpav
approved these changes
May 13, 2026
Contributor
mattrpav
left a comment
There was a problem hiding this comment.
LGTM. Good change to use the same uri parser that is used to construct the objects
cshannon
added a commit
that referenced
this pull request
May 13, 2026
cshannon
added a commit
that referenced
this pull request
May 13, 2026
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
2 participants
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.
Parentheses are optional when creating composite and nested URIs so this updates the validation to handle missing parens as well.
Follow on to #1847