-
Notifications
You must be signed in to change notification settings - Fork 25.2k
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
Blazor RC2 Updates 8.0 #30576
Blazor RC2 Updates 8.0 #30576
Conversation
@@ -1478,9 +1476,6 @@ In the preceding code, the CSS selector, `#app`, indicates that the `App` compon | |||
<div id="app">...</app> | |||
``` | |||
|
|||
<!-- UPDATE 8.0 Need to check on this: Is this still valid in a | |||
BW app, and is the render-mode still set in this way? --> | |||
|
|||
MVC and Razor Pages apps can also use the [Component Tag Helper](xref:Microsoft.AspNetCore.Mvc.TagHelpers.ComponentTagHelper) to register statically-rendered Blazor WebAssembly root components: |
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.
Yeah, I'm not sure why this specifically refers to using the component tag helper with statically rendered Blazor WebAssembly components. The component tag helper supports the interactive server and WebAssembly render modes. It doesn't support Auto.
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.
Let's discuss this further. This whole section is specifically about rendering static root components. I thought it was correct in that context.
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.
Looks good. I have some comments, but this is all in the right direction.
Co-authored-by: Daniel Roth <[email protected]>
Co-authored-by: Daniel Roth <[email protected]>
Co-authored-by: Daniel Roth <[email protected]>
Co-authored-by: Daniel Roth <[email protected]>
Co-authored-by: Daniel Roth <[email protected]>
Co-authored-by: Daniel Roth <[email protected]>
Co-authored-by: Daniel Roth <[email protected]>
Co-authored-by: Daniel Roth <[email protected]>
@danroth27 ... Reacted to feedback. Sorry for so many commits to get your suggestions batched. GH was throwing an error but wouldn't tell me which suggestion was failing. I had to block them out in groups to narrow it down to the one that was choking. I'm going to start the Release Notes update now but finish it on Monday morning. Will be on PR #30619, and I'll merge it Monday morning but circle around with cross-links for any new sections after RC2 releases. I'll go back over this entire PR looking for further improvements and gremlins 😈 . For some highlights ..................... Blazor identity UIAdded to Release Notes - Done! 👍; however, I probably need to discuss with Halter to confirm that I'm writing the articles for the security node to cover the new API. Support for dialog cancel and close events... moving to Release Notes. - Done! 👍 Statically-rendered root componentsFor ...
... that whole section is about statically-rendered root components, so I thought this remark in that context was correct. automatic (Auto)... going back to just Auto. New section on custom shorthand render modes... check again to see if the rewrite is correct. It's still might be rough, and you still might decide just to nix it. I liked it for a shorthand no-prerender approach, but it might not be worth it. As Steve said, how often will folks be disabling prerendering? Also, it's probably going to be more useful if more flags are added, but that might never happen. Forms articleMoved the Enhanced navigation and form handling section to the bottom and dropped it from the example forms. ... AND ... WRT reorganizing the coverage ... I recommend doing it during RC2, not for this PR. However, I'll try to squeeze it in now if you want. Opened Reorganize Blazor forms coverage 8.0 #30618.
|
Addresses #28161
Fixes #30372
Addresses #30002
Notes
JS initializers coverage will be added on Monday.For RTMI'll update and cross-link the passing tokens guidance on Monday.Done! 👍The tracking issue has been updated ...
Blazor .NET 8 tracking issue
#28161
Internal previews
Toggle expand/collapse
QuickGrid
component[JSImport]
/[JSExport]
interop with ASP.NET Core Blazor