Skip to content
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

Adding partial namespaces in Blazor's razor markup #22194

Closed
simonziegler opened this issue May 25, 2020 · 3 comments
Closed

Adding partial namespaces in Blazor's razor markup #22194

simonziegler opened this issue May 25, 2020 · 3 comments
Labels
affected-few This issue impacts only small number of customers area-blazor Includes: Blazor, Razor Components enhancement This issue represents an ask for new feature or an enhancement to an existing one feature-razor.language severity-major This label is used by an internal tool

Comments

@simonziegler
Copy link

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

Not a problem, but this would improve maintainability for a moderate to large project composed from multiple libraries (both regular C# netstandard and razor libraries).

Describe the solution you'd like

Blazor's Razor markup doesn't support partial namespaces. I am building a suite of libraries and would like all of them to share a single top level namespace, say foo. The libraries would then apply namespaces:

  • Library 1: namespace foo.bar1 with components Bish.razor, Bash.razor and Bosh.razor.
  • Library 2: namespace foo.bar2
  • Library 3: namespace foo.bar3

The app consuming the libraries would then place @using foo and use the remainder of the namespace in a component tag. So for instance using the component Bish from library 1, the markup would be <bar1.Bish ... />.

This is geared towards maintainability and clarity of usage.

Additional context

https://docs.microsoft.com/en-us/aspnet/core/blazor/components?view=aspnetcore-3.1#import-components.

@javiercn javiercn added the area-blazor Includes: Blazor, Razor Components label May 25, 2020
@mkArtakMSFT mkArtakMSFT added the enhancement This issue represents an ask for new feature or an enhancement to an existing one label May 26, 2020
@mkArtakMSFT mkArtakMSFT added this to the Backlog milestone May 26, 2020
@mkArtakMSFT
Copy link
Member

We've moved this issue to the Backlog milestone. This means that it is not going to happen for the coming release. We will reassess the backlog following the current release and consider this item at that time. However, keep in mind that there are many other high priority features with which it will be competing for resources.

@simonziegler
Copy link
Author

Thanks @mkArtakMSFT

@captainsafia captainsafia added affected-few This issue impacts only small number of customers severity-major This label is used by an internal tool labels Oct 7, 2020
@mkArtakMSFT mkArtakMSFT modified the milestones: Backlog, BlazorPlanning Nov 5, 2023
@mkArtakMSFT
Copy link
Member

Hi. Thanks for contacting us.
We're closing this issue as there was not much community interest in this ask for quite a while now.
You can learn more about our triage process and how we handle issues by reading our Triage Process writeup.

@mkArtakMSFT mkArtakMSFT closed this as not planned Won't fix, can't repro, duplicate, stale Nov 30, 2023
@ghost ghost locked as resolved and limited conversation to collaborators Feb 7, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
affected-few This issue impacts only small number of customers area-blazor Includes: Blazor, Razor Components enhancement This issue represents an ask for new feature or an enhancement to an existing one feature-razor.language severity-major This label is used by an internal tool
Projects
None yet
Development

No branches or pull requests

4 participants