Skip to content

'Razor component' versus 'Blazor component' in project templates #31559

Closed
@guardrex

Description

@guardrex

Is your feature request related to a problem? Please describe.

Feature description question

Describe the solution you'd like

The RCL project template and the WebView sample component have a components with the following markup:

<div class="my-component">
    This Blazor component is defined in the <strong>WebviewAppShared</strong> package.
</div>
<div class="my-component">
    This Blazor component is defined in the <strong>Company.RazorClassLibrary1</strong> library.
</div>

We don't currently use the naming 'Blazor component' in docs. We use 'Razor component' everywhere. I wonder if these framework components should use 'Razor component'? If not, what doc contexts should use 'Blazor component'?

Additional context

Also note that a few other spots use 'Blazor component' lingo. For example, I saw 'Blazor component model' go by in search results.

Metadata

Metadata

Assignees

No one assigned

    Labels

    area-blazorIncludes: Blazor, Razor Componentsgood first issueGood for newcomers.help wantedUp for grabs. We would accept a PR to help resolve this issue

    Type

    No type

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions