[automated] Merge branch 'release/8.0' => 'main' #50838
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
…tnet#48029)" (dotnet#50723) This reverts commit 42d14c4.
[Blazor] Adds support for persting prerendered state on Blazor Web applications. * Persists state both for server and webassembly as necessary. * Initializes the state when a given interactive runtime is initialized and renders the first set of components. * On WebAssembly, this is the first time the app starts. * On Server this happens every time a circuit starts. * The state is available during the first render, until the components reach quiescence. The approach we follow is different for server and webassembly: * On Server, we support initializing the circuit with an empty set of descriptors and in that case, we delay initialization until the first `UpdateRootComponents` call is issued. * This is because it's hard to deal with the security constraints imposed by starting a new circuit multiple times, and its easier to handle them within UpdateRootComponents. We might switch this approach in the future to go through `StartCircuit` too. * On WebAssembly, we query for the initial set of webassembly components when we are starting the runtime in a Blazor Web Scenario. * We do this because Blazor WebAssembly offers a programatic API to render root components at a given location defined by their selectors, so we need to make sure that those components can receive state at the same time the initial set of WebAssembly components added to the page. There are a set of tests validating different behaviors with regards to enhanced navigation and streaming rendering, as well as making sure that auto mode can access the state on Server and WebAssembly, and that Server gets new state every time a circuit is opened.
* Make IEmailSender more customizable * Remove unnecessary metadata * Add TUser parameter * React to API review feedback * Fix IdentitySample.DefaultUI
[release/8.0] Update dependencies from dotnet/arcade - Update EventTest.cs now that Selenium reports the full set of events properly - Update EventTest.cs - Quarantine (actually comment out) one of the CanRenderComponentWithPersistedState cases See dotnet#50810 - Disable another flaky test
…0823) * Handle obsolete InterceptorsPreview with .NET 8 RC2 SDK (dotnet#50797) * Quarantine (actually comment out) one of the CanRenderComponentWithPersistedState cases (dotnet#50811) See dotnet#50810 * Stop processing original response streaming content if user has started navigating away (dotnet#50814) * Reproduce dotnet#50733 as a failing E2E test * Don't process original request blazor-ssr content if the user has already navigated away * Quarantine (actually comment out) one of the CanRenderComponentWithPersistedState cases See dotnet#50810 * Update EventTest.cs * Disable another flaky test --------- Co-authored-by: Matt Thalman <[email protected]> Co-authored-by: Steve Sanderson <[email protected]>
dotnet-maestro-bot
force-pushed
the
merge/release/8.0-to-main
branch
from
6470546 to
2773e8a
Compare
ghost
added
area-infrastructure
…otnet#50829) [release/8.0] Update dependencies from dotnet/source-build-externals - Update EventTest.cs
[release/8.0] Update dependencies from dotnet/arcade - Update EventTest.cs now that Selenium reports the full set of events properly - Update EventTest.cs - Quarantine (actually comment out) one of the CanRenderComponentWithPersistedState cases See dotnet#50810 - Disable another flaky test
…0823) * Handle obsolete InterceptorsPreview with .NET 8 RC2 SDK (dotnet#50797) * Quarantine (actually comment out) one of the CanRenderComponentWithPersistedState cases (dotnet#50811) See dotnet#50810 * Stop processing original response streaming content if user has started navigating away (dotnet#50814) * Reproduce dotnet#50733 as a failing E2E test * Don't process original request blazor-ssr content if the user has already navigated away * Quarantine (actually comment out) one of the CanRenderComponentWithPersistedState cases See dotnet#50810 * Update EventTest.cs * Disable another flaky test --------- Co-authored-by: Matt Thalman <[email protected]> Co-authored-by: Steve Sanderson <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
6 participants
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.
I detected changes in the release/8.0 branch which have not been merged yet to main. I'm a robot and am configured to help you automatically keep main up to date, so I've opened this PR.
This PR merges commits made on release/8.0 by the following committers:
Instructions for merging from UI
This PR will not be auto-merged. When pull request checks pass, complete this PR by creating a merge commit, not a squash or rebase commit.
If this repo does not allow creating merge commits from the GitHub UI, use command line instructions.
Instructions for merging via command line
Run these commands to merge this pull request from the command line.
or if you are using SSH
After PR checks are complete push the branch
Instructions for resolving conflicts
Instructions for updating this pull request
Contributors to this repo have permission update this pull request by pushing to the branch 'merge/release/8.0-to-main'. This can be done to resolve conflicts or make other changes to this pull request before it is merged.
or if you are using SSH
Contact .NET Core Engineering if you have questions or issues.
Also, if this PR was generated incorrectly, help us fix it. See https://github.com/dotnet/arcade/blob/master/scripts/GitHubMergeBranches.ps1.