feat(router): allow string destination in RedirectCommand - #70321
Open
atscott wants to merge 1 commit into
Open
Conversation
RedirectCommand now accepts a URL string starting with '/' in addition to UrlTree. This improves developer experience by allowing guards, resolvers, and error handlers to redirect to absolute paths without requiring the Router to be injected solely to call parseurl().
BREAKING CHANGE: `RedirectCommand.redirectTo` can now be a string
The `redirectTo` property on `RedirectCommand` can now be a `string` (specifically `UrlTree | '/${string}'`). Any code reading `RedirectCommand.redirectTo` directly may need to handle `string` values in addition to `UrlTree`.
atscott
marked this pull request as ready for review
August 20, 2026 20:54
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
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.
RedirectCommand now accepts a URL string starting with '/' in addition to UrlTree. This improves developer experience by allowing guards, resolvers, and error handlers to redirect to absolute paths without requiring the Router to be injected solely to call parseurl().
BREAKING CHANGE:
RedirectCommand.redirectTocan now be a stringThe
redirectToproperty onRedirectCommandcan now be astring(specificallyUrlTree | '/${string}'). Any code readingRedirectCommand.redirectTodirectly may need to handlestringvalues in addition toUrlTree.