Skip to content

Conversation

@atscott
Copy link
Contributor

@atscott atscott commented Oct 28, 2025

this adds support for both leading and trailing segments before/after wildcard route. Exposig the segments in a new _splat param would require a breaking change to the return value of the matchers.

fixes #60821

this adds support for both leading and trailing segments before/after wildcard
route. Exposig the segments in a new _splat param would require a
breaking change to the return value of the matchers.

fixes angular#60821
@atscott atscott added requires: TGP This PR requires a passing TGP before merging is allowed target: minor This PR is targeted for the next minor release and removed state: blocked labels Oct 28, 2025
@atscott atscott marked this pull request as ready for review October 29, 2025 16:12
@pullapprove pullapprove bot removed the requires: TGP This PR requires a passing TGP before merging is allowed label Oct 29, 2025
@atscott atscott added the target: feature This PR is targeted for a feature branch (outside of main and semver branches) label Oct 29, 2025
@atscott atscott added action: merge The PR is ready for merge by the caretaker target: minor This PR is targeted for the next minor release and removed target: minor This PR is targeted for the next minor release target: feature This PR is targeted for a feature branch (outside of main and semver branches) labels Oct 29, 2025
@atscott
Copy link
Contributor Author

atscott commented Oct 30, 2025

This PR was merged into the repository. The changes were merged into the following branches:

@atscott atscott closed this in c84d372 Oct 30, 2025
Comment on lines +617 to +620
{
path: '**/b',
component: ComponentB,
},
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hi @atscott . Thank you for supporting more sophisticated wildcard route paths, so that we don't need to build custom UrlMatchers in such cases (that are tricky to write and test).

FYI In our Spartacus library in the past we've built custom "suffix url matchers", e.g. to match a pattern like **/p/:productCode.

So let me ask a question for our usecase: Is this PR supporting also dynamic params (:param) as the URL segments? I'm asking, as I'm having problem to find unit tests for this case.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No, this only supports static suffixes

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

action: merge The PR is ready for merge by the caretaker target: minor This PR is targeted for the next minor release

3 participants