-
-
Notifications
You must be signed in to change notification settings - Fork 241
fix(location-strategy): extend support for nested primary outlets #1717
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
Conversation
release: cut the 7.2.0 release
fd1a010
to
03915a1
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
After all tests are green
<page-router-outlet tag="rootPRO"></page-router-outlet> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is the tag="rootPRO"
used somewhere or just for debugging?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
it is just for debugging, since it is very easy to distinguish which p-r-o is activated, states and so on..it's also in the test app only
bb0db35
to
901277d
Compare
test |
901277d
to
df484d3
Compare
test package_version#rc |
Extending
LocationState
withFrame
property which holds theFrame
that initiated the navigation for the givenLocationState
. Back in parent Outlet should take care of its children states (remove all states until the currentFrame
that goes back is reached).Various bug with nested primary
<page-router-outlets>
where reported from both Kinvey Shared Application and the North Star project.