Closed guardrex closed 3 years ago
@guardrex thanks for bringing this up.
These should be renamed to razor component
Could we rename this to "This component" (so we don't use either Blazor or Razor) here?
Thanks for contacting us.
We're moving this issue to the Next sprint planning
milestone for future evaluation / consideration. Because it's not immediately obvious that this is a bug in our framework, we would like to keep this around to collect more feedback, which can later help us determine the impact of it. We will re-evaluate this issue, during our next planning meeting(s).
If we later determine, that the issue has no community involvement, or it's very rare and low-impact issue, we will close it - so that the team can focus on more important and high impact issues.
To learn more about what to expect next and how this issue will be handled you can read more about our triage process here.
I would like to take this on and create a PR - is that OK ?
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:
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.