Skip to content

fix(@angular/ssr): enhance dynamic route matching for better performance and accuracy #29461

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

Merged
merged 1 commit into from
Jan 24, 2025

Conversation

alan-agius4
Copy link
Collaborator

Updated route matching logic to prioritize closest matches, improving the accuracy of dynamic route resolution. Also we optimized performance by eliminating unnecessary recursive checks, reducing overhead during route matching.

Closes #29452

@alan-agius4 alan-agius4 force-pushed the matchers branch 2 times, most recently from 0d2acbb to 6b9be13 Compare January 23, 2025 09:55
@alan-agius4 alan-agius4 requested a review from dgp1130 January 23, 2025 09:55
@alan-agius4 alan-agius4 added the action: review The PR is still awaiting reviews from at least one requested reviewer label Jan 23, 2025
@alan-agius4 alan-agius4 marked this pull request as ready for review January 23, 2025 09:55
@alan-agius4 alan-agius4 added the target: patch This PR is targeted for the next patch release label Jan 23, 2025
@alan-agius4 alan-agius4 force-pushed the matchers branch 6 times, most recently from 76a7d9d to b01f492 Compare January 23, 2025 13:07
@alan-agius4 alan-agius4 reopened this Jan 23, 2025
Copy link
Collaborator

@dgp1130 dgp1130 left a comment

Choose a reason for hiding this comment

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

It seems like there's a few small breaking changes here. I know this feature is still dev preview, so we can probably ship this and I'm happy to defer to your judgement. I just want to make sure we're thinking about the impact here and making that decision intentionally.

…nce and accuracy

Updated route matching logic to prioritize closest matches, improving the accuracy of dynamic route resolution. Also we optimized performance by eliminating unnecessary recursive checks, reducing overhead during route matching.

Closes angular#29452
@alan-agius4 alan-agius4 added action: merge The PR is ready for merge by the caretaker and removed action: review The PR is still awaiting reviews from at least one requested reviewer labels Jan 24, 2025
@alan-agius4 alan-agius4 merged commit 4df97d1 into angular:main Jan 24, 2025
31 checks passed
@alan-agius4 alan-agius4 deleted the matchers branch January 24, 2025 10:44
@alan-agius4
Copy link
Collaborator Author

The changes were merged into the following branches: main, 19.1.x

@angular-automatic-lock-bot
Copy link

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

This action has been performed automatically by a bot.

@angular-automatic-lock-bot angular-automatic-lock-bot bot locked and limited conversation to collaborators Feb 24, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
action: merge The PR is ready for merge by the caretaker area: @angular/ssr target: patch This PR is targeted for the next patch release
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Routes beginning with Dynamic Parameters break Angular Prerendering and SSR
2 participants