[release/7.0-preview6] Backport custom HTML elements rendering Blazor components #42383
Conversation
This file contains 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
MackinnonBuck
requested review from
a team,
dougbu,
wtgodbe and
Pilchie
as code owners
MackinnonBuck
added
Servicing-approved
|
@MackinnonBuck I can approve and merge this but need your confirmation that (other than whitespace) this change is identical to what was merged earlier today into 'main' (8942608). Please let me know. If there are a few differences, please point them out&helllip; |
|
@dougbu This change is identical to the one merged into main earlier today. |
dougbu
approved these changes
Jun 24, 2022
|
I didn't see anything suspicious in the CI failure and am rerunning failed jobs there. Enabled auto-merge here. |
|
/azp run |
|
Azure Pipelines successfully started running 2 pipeline(s). |
|
@MackinnonBuck please merge #42459 into this. I didn't realize the two PRs were tightly bound. /cc @mmitche |
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.
Custom HTML elements rendering Blazor components
This PR productizes the custom elements support package. Backport of #42314
Description
This package provides a simple mechanism for using Blazor components as custom elements. This means you can easily render Blazor components dynamically from other SPA frameworks, such as Angular or React.
Fixes #38447
Customer Impact
This package brings value to the scenario where Blazor components are gradually introduced into existing projects written in other SPA frameworks. Rather than having to manually manage the state and lifecycle of Blazor root components using JavaScript APIs, it can now be done in a more intuitive fashion using custom HTML elements. By making this package official and built with the rest of the repository, customers can trust that it will be stable and up to date with the latest version of Blazor.
Regression?
Risk
These changes do not touch the core framework. The new code remains almost unchanged from the existing support package, so it's unlikely we're introducing new bugs.
Verification
Packaging changes reviewed?