fix(router): ensure check for match options is compatible with proper… #43086
Conversation
AndrewKushnir
approved these changes
Aug 9, 2021
LGTM
One nit: may be add a quick comment on why this change was made and that further refactoring might affect Closure compiler-generated code (so we don't break it accidentally).
…ty renaming After renaming, 'paths' is not in routerLinkOptions since it's been renamed.
This issue has been automatically locked due to inactivity. Read more about our automatic conversation locking policy. This action has been performed automatically by a bot. |
TeriGlover
added a commit
to TeriGlover/angular
that referenced
this issue
Sep 16, 2021
…ty renaming (angular#43086) After renaming, 'paths' is not in routerLinkOptions since it's been renamed. PR Close angular#43086
TeriGlover
added a commit
to TeriGlover/angular
that referenced
this issue
Sep 22, 2021
…ty renaming (angular#43086) After renaming, 'paths' is not in routerLinkOptions since it's been renamed. PR Close angular#43086
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
…ty renaming
After renaming, 'paths' is not in routerLinkOptions since it's been renamed.
The text was updated successfully, but these errors were encountered: