Migrate to cascading auth state services#31065
Merged
Conversation
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.
Fixes #31056
Thanks @xunmeng2002! 🚀 ... I'm sorry that we didn't have these updates! It didn't make some of the product unit lists that I received, so it slipped through the cracks and didn't get covered for release.
This PR should cover it now everywhere that we had guidance on the
CascadingAuthenticationStatecomponent, AND I added a section to the 8.0 Migration article to highlight it.I'm going to merge this quickly 🏃 and take it live immediately. It should appear in the live articles within 20 minutes.
Internal previews