Use "Razor component" and avoid "Blazor component" #4830
Labels
area-blazor
Blazor Hybrid / Desktop, BlazorWebView
fixed-in-6.0.200-preview.14.2
Look for this fix in 6.0.200-preview.14.2!
proposal/open
Description
I'm going to move this over from a GH discussion because I'm having good luck 🍀 thus far getting MS pubs updated on the point, and I hope we'll be able to address the lingering instances of "Blazor component" in frameworks. Separately, I've opened this for the ASP.NET Core team (
dotnet/aspnetcore
) at dotnet/aspnetcore#40344, and they've agreed to my sending a PR to update it there.Mirroring the discussion remarks that I posted at #4799 ...
The term "Blazor component" is valid informal naming for Razor components, which is the official, formal name. See my remarks here ...
dotnet/docs-maui#295
I recommend that in the few spots in framework code where the term "Blazor component" appears that it be changed to either "Razor component" or just "component" to resolve the dual-naming problem and completely align the framework code/API docs with the Blazor docs.
Public API Changes
"Blazor component" only appears in three files here, usually in comments that will resolve to API docs ...
If you'd entertain a PR from me to update these spots, I'll create a PR to knock it out 🥊. Let me know 📣👂.
Intended Use-Case
"Blazor component" has slipped out a little bit into the community, but I think we can head off further wide adoption by stomping it out NOW 🏃 ... quickly 🏃🏃. Future generations will thank us! 😄
The text was updated successfully, but these errors were encountered: