Skip to content

[Components] Enable a root component to be the entry point for component based apps #7528

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

Closed
5 tasks
javiercn opened this issue Feb 13, 2019 · 3 comments
Closed
5 tasks
Labels
affected-most This issue impacts most of the customers area-blazor Includes: Blazor, Razor Components enhancement This issue represents an ask for new feature or an enhancement to an existing one feature-prerendering Issues related to prerendering blazor components severity-nice-to-have This label is used by an internal tool

Comments

@javiercn
Copy link
Member

javiercn commented Feb 13, 2019

This is a tracking issue for enabling applications that only use components end to end. Here we will discuss and track the work that needs to be done to enable this scenario:

  • Support DOCTYPE declarations.
  • Support a way to mark a component as a "root component" so that it can be used as the container for the entire app.
  • Figure out a way to turn prerrendering on and off selectively.
  • Figure out what component equivalents we need for things like the Environment tag helper, '~/' etc.
  • Figure out specific integrations with endpoint routing.
@Andrzej-W
Copy link

The concept of "root component" is very nice. Please remember about SEO. Prerendered HTML page has to have correct title, description, metatags. More about this here: https://github.com/aspnet/Blazor/issues/1311#issuecomment-413046895

@Eilon Eilon added the area-mvc Includes: MVC, Actions and Controllers, Localization, CORS, most templates label Feb 13, 2019
@mkArtakMSFT mkArtakMSFT added the area-blazor Includes: Blazor, Razor Components label Feb 13, 2019
@mkArtakMSFT mkArtakMSFT added this to the 3.0.0-preview4 milestone Feb 13, 2019
@mkArtakMSFT mkArtakMSFT added 1 - Ready enhancement This issue represents an ask for new feature or an enhancement to an existing one labels Feb 13, 2019
@mkArtakMSFT mkArtakMSFT modified the milestones: 3.0.0-preview4, Backlog Feb 22, 2019
@mkArtakMSFT mkArtakMSFT removed area-mvc Includes: MVC, Actions and Controllers, Localization, CORS, most templates labels May 9, 2019
@SteveSandersonMS SteveSandersonMS added affected-most This issue impacts most of the customers severity-nice-to-have This label is used by an internal tool labels Oct 6, 2020 — with ASP.NET Core Issue Ranking
@javiercn javiercn added the feature-prerendering Issues related to prerendering blazor components label Apr 19, 2021
@mkArtakMSFT mkArtakMSFT modified the milestones: Backlog, .NET 8 Planning Oct 6, 2022
@ghost
Copy link

ghost commented Oct 6, 2022

Thanks for contacting us.

We're moving this issue to the .NET 8 Planning milestone for future evaluation / consideration. We would like to keep this around to collect more feedback, which can help us with prioritizing this work. 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.

@mkArtakMSFT
Copy link
Contributor

Closing as this should be already done.

@ghost ghost locked as resolved and limited conversation to collaborators Jul 30, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
affected-most This issue impacts most of the customers area-blazor Includes: Blazor, Razor Components enhancement This issue represents an ask for new feature or an enhancement to an existing one feature-prerendering Issues related to prerendering blazor components severity-nice-to-have This label is used by an internal tool
Projects
None yet
Development

No branches or pull requests

8 participants