Skip to content

Conversation

alan-agius4
Copy link
Collaborator

@alan-agius4 alan-agius4 commented Dec 9, 2024

To prevent navigating to the root page while extracting routes, a non-existent path (/ng-routes-internal) is intentionally used. This ensures unnecessary rendering during the route extraction process where now only the app component is rendered.

@alan-agius4 alan-agius4 added the target: patch This PR is targeted for the next patch release label Dec 9, 2024
To prevent rendering the root route while extracting routes, a non-existent path (`/ng-extract-routes`) is intentionally used. This ensures unnecessary rendering during the route extraction process where now only the app component is rendered.
@alan-agius4 alan-agius4 closed this Dec 9, 2024
@alan-agius4 alan-agius4 changed the title refactor(@angular/ssr): skip rendering root page during route extraction refactor(@angular/ssr): skip navigating to the root page during route extraction Dec 9, 2024
@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 Jan 9, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

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.

1 participant