-
Notifications
You must be signed in to change notification settings - Fork 25.3k
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 project tracking 2023 #28001
Labels
Comments
This was referenced Jan 19, 2023
Merged
This was referenced Jan 28, 2023
This was referenced Feb 15, 2023
Merged
This was referenced Feb 23, 2023
Merged
This was referenced Mar 4, 2023
This was referenced Mar 13, 2023
Merged
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
2023
History
Doc ideas
Not ALL of these will be worked. This is an idea list/check list that don't rise to the level of opening an issue at this time.
./
, but shouldn't we remove the./
in the general case?<head>
content for the JS collocation example.<HeadContent><script src="./Components/Pages/JsCollocation1.razor.js"></script></HeadContent>
OnInitialized
orOnParametersSetAsync
blazor ssr form processing issues aspnetcore#51978base.OnAfterRenderAsync(firstRender);
need to be called? No, we try to avoid making people call base onComponentBase
virtual methods. They can call it if they want but it’s a no-op.dotnet/blazor-samples
repo. Check for (and send) empty body on log out post. blazor-samples#136<Router>
(or routing or router)" language for cross-links to new guidance in the Fundamentals > Routing article.AuthorizeView
coverage for error/API described in ClientID vs SecretID #31119..Client
) project is mentioned for BWAs and confirm that they're all described as the "server project.".Client
project really can host interactive server components.IdentityUser
forAppUser
-AND- I need to cross-link in the article's remark for "advanced Identity features" to whatever the main doc set is going to have on the subject in the SPA/Identity docs. SPA authentication and authorization doc #31010 (comment)AddControllersAndViews
and pass the anti-forgery token to the Blazor app (<8.0) or obtain it from the anti-forgery feature (>=8.0) for the POST._
/this
all the things ... Fix naming violations in sample code (_camelCase with underscore for private fields) #30533 (comment)<NotFound>
going away for BWA at 8.0, I think a dedicated bit in the Error handling topic on processing 404s via built-in server middleware makes sense (i.e.,UseStatusCodePagesWithRedirects
). Be sure to search for it because a cross-link is required in at least one case where I left a NOTE about BWAs not using the Not Found content template any longer.__builder
changeover to Razor template. It's versioned 6.0, but the template approach works at 5.0. Find out if it works as far back at 3.1 ... if so, 🔪 the__builder
approach for all versions. UPDATE: Confirmed working for all versions. Remove prior reusable RenderFragment approach #30121builder.AddMarkupContent(0, someUserSuppliedString)
because it can create an XSS vulnerability.<xref:fundamentals/target-aspnetcore>
) in the class lib article. Cross-link content #29697file://
pages for debugging on the client.<textarea>
content in a form of Message size limit enhancements #29541. LiveMicrosoft.Identity.Web.MicrosoftIdentityWebApiAuthenticationBuilderExtensions.AddMicrosoftIdentityWebApi
. I'm code-fencing the method name for now. Tracking: Missing API for WebApiExtensions/MicrosoftIdentityWebApiAuthenticationBuilderExtensions AzureAD/microsoft-identity-web#2265 PR: Restore API cross-links #29473element-component-model-relationships.md
,overwriting-parameters.md
,synchronization-context.md
,splat-attributes-and-arbitrary-parameters.md
PR: Move code example cross-links in new articles #29437https://github.com/dotnet/aspnetcore/issues/47803
dotnet/blazor-samples
repo and update links. PR: Move sample apps to samples repo #29268NavigateTo
uses optional leading forward-slash URLs. Hashed routing to named elements #29106 (comment) Analysis: Looks good, and we have specific guidance on relative app base path scenarios. No action needed. 👍razor
code language. PR: Code language updates #29210HttpClient
text and examples for hosted WASM guidance in the Call a web API topic and see if{APP NAME}
forms part of the named client. Go with{PROJECT NAME}
instead to better match what devs supply to VS on solution creation. PR: Change "app name" placeholder to "project name" #28884server
" and "webassembly
" in the{webassembly|server}
Blazor script placeholder in the JS interop overview article. PR: Update placeholder #28911.mjs
instead of.js
for module files. https://github.com/dotnet/aspnetcore/blob/main/src/Middleware/StaticFiles/src/FileExtensionContentTypeProvider.cs#L178 Do that this year? PR: Add remark on module extension '.mjs' #29023 We'll stick with .js for a while longer.<head>
content for Blazor Server to version between_Host.cshtml
(not 6.0) and_Layout.cshtml
(6.0) with: In the `<head>` markup ([location of `<head>` content](xref:blazor/project-structure#location-of-head-content)), ... Addressed on Location of SignalR client builder #28498. Will pick up remaining updates while removing Whole-topic Versioning from remaining docs.AuthenticationStateProvider
example (PU Issue): We have one ... a very simple, kind'a unrealistic one. We also now have a notification version of it, so that's good. I just wonder if we should have more of a real-world example of something that devs are commonly having to do with it? Won't fix because the notification example added earlier is a real world scenario for the approach.TokenProvider
in the current guidance, so it seems that the component calls a server API to hit up the IdP to renew (and get a new refresh token) with an update to theTokenProvider
with the new tokens. The component continues processing transparently (re-initiates the web API call that it was making in the first place) after the server-side work. Cross-refs: Miss a strategy to handle the refresh of tokens #19797 (comment)@attribute [IgnoreAntiforgeryToken]
, including for logout. The coverage is at: https://learn.microsoft.com/en-us/aspnet/core/security/authentication/scaffold-identity?view=aspnetcore-7.0&tabs=visual-studio#pass-an-xsrf-token-to-the-appHttpContext
/IHttpContextAccessor
to the existing Blazor doc remarks. Addressed by Blazor Server security updates. However, [SignalR][Blazor] HttpContext and IHttpContextAccessor #14974 remains open for a section in the SignalR docs.{APP ASSEMBLY}
into{ASSEMBLY NAME}
everywhere. Fixed on Change placeholder #28435.Blazor.start().then
versus theafterStarted
approach with a JS initializer. Cross-link JS initializer coverage #28275<span aria-hidden="true">XXXXX</span><span class="visually-hidden">XXXXX</span>
PR: Binding guidance improvements #27991FileSystem
API use in Blazor apps?testassets
pieces in the framework to see what might be helpful for devs to see in docs. It's a large task tho because there's so much there. This probably can't be worked in 23H1, possibly for 23Q3 tho.dotnet/blazor-samples
-based, fully working, cut-'n-paste examples. Might be best to create a list on an issue first, then I can work down the list.QuickGrid
example that opens and closes a detail record component without losing the page and scroll position of the grid. For context, see Blazor database example's list page is reloaded when coming back from a details page blazor-samples#58./p:RuntimeIdentifier={RID}
but the self-contained setting doesn't (/p:SelfContained=false
).UE pass tracking
App
component example INCLUDE(s) to cover 6.0 churn. See: Missing code which is generated from project template #23696. Work Add an AAD scenario: authorized client apps for APIs #25026 in this node. There are general remarks and some specific items for AAD/AAD B2C andUserManager
/SignInManager
at Confusing instructions, Code example cause internal Server error #27279.HttpResponseMessage
" language in the API doc, per discussion at Confusing AuthorizationMessageHandler remark #26739 (and respond back on that issue with the final answer from the PU).tasks.json
/launch.json
due to Errors when running .net generate assets to build .vscode folder vscode-csharp#4542. See 👉 small clarification #23777TestServer
). Missing example on how to use TestServer with ASP.NET 6 #25263NavigationManager.NavigateTo
. See :point-right: Use relative path in NavigateTo #22146 (comment).web.config
post PR Remove .wasm file extension before redefining it #24950 and in light of discussion on https://stackoverflow.com/a/69888016 and https://stackoverflow.com/a/70967738. Probably add a tagged SO filter link:https://stackoverflow.com/questions/tagged/blazor+iis+compression
SEPARATE WORK ITEM FOR SECURITY NODE
UE pass tracking
New topics added recently that haven't had the 🦖 Rex Treatment™ 🦖 ... or at least haven't had a pass for a few years ...
The text was updated successfully, but these errors were encountered: