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.

Sign up for GitHub

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

Jump to bottom

Scaffolding for Razor Components #6921

Closed
SteveSandersonMS opened this issue Jan 22, 2019 · 8 comments
Closed

Scaffolding for Razor Components #6921

SteveSandersonMS opened this issue Jan 22, 2019 · 8 comments
Labels
affected-medium This issue impacts approximately half of our customers area-blazor Includes: Blazor, Razor Components enhancement This issue represents an ask for new feature or an enhancement to an existing one feature-blazor-tooling Blazor specific tooling requests Pillar: Dev Experience severity-minor This label is used by an internal tool
Milestone
.NET 9 Planning

Comments

@SteveSandersonMS
Copy link
Member

It should be possible to scaffold a CRUD UI in much the same way as for MVC.
@SteveSandersonMS SteveSandersonMS added 0 - Backlog enhancement This issue represents an ask for new feature or an enhancement to an existing one area-mvc Includes: MVC, Actions and Controllers, Localization, CORS, most templates labels Jan 22, 2019
@danroth27 danroth27 mentioned this issue Jan 22, 2019
Closed
@danroth27
Copy link
Member

Maybe something like: https://api-platform.com/docs/client-generator/react/

@SteveSandersonMS SteveSandersonMS added the area-blazor Includes: Blazor, Razor Components label Feb 6, 2019
@mkArtakMSFT mkArtakMSFT added this to the Backlog milestone Mar 12, 2019
@mkArtakMSFT mkArtakMSFT removed area-mvc Includes: MVC, Actions and Controllers, Localization, CORS, most templates labels May 9, 2019
@pranavkm pranavkm added the help wanted Up for grabs. We would accept a PR to help resolve this issue label Jul 6, 2020
@AniAchar
Copy link

@SteveSandersonMS I would like to pick this issue up as part of the July 2020 sprint.

@captainsafia captainsafia removed the help wanted Up for grabs. We would accept a PR to help resolve this issue label Sep 9, 2020
@SteveSandersonMS SteveSandersonMS added affected-medium This issue impacts approximately half of our customers severity-minor This label is used by an internal tool labels Oct 14, 2020 — with ASP.NET Core Issue Ranking
@javiercn javiercn added the feature-blazor-tooling Blazor specific tooling requests label Apr 19, 2021
@TanayParikh TanayParikh modified the milestones: Backlog, .NET 7 Planning Oct 19, 2021
@ghost
Copy link

ghost commented Oct 21, 2021

We've moved this issue to the Backlog milestone. This means that it is not going to be worked on for the coming release. We will reassess the backlog following the current release and consider this item at that time. To learn more about our issue management process and to have better expectation regarding different types of issues you can read our Triage Process.

@mkArtakMSFT mkArtakMSFT mentioned this issue Nov 16, 2021
Closed
@mkArtakMSFT mkArtakMSFT modified the milestones: Backlog, .NET 8 Planning Oct 19, 2022
@ghost
Copy link

ghost commented Oct 19, 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.

@guardrex guardrex mentioned this issue Apr 18, 2023
Closed
@johnmagesh
Copy link

This will be a great feature to have and would make development faster and would attract more audience.

@mkArtakMSFT mkArtakMSFT modified the milestones: .NET 8 Planning, Backlog Jun 29, 2023
@ghost
Copy link

ghost commented Jun 29, 2023

We've moved this issue to the Backlog milestone. This means that it is not going to be worked on for the coming release. We will reassess the backlog following the current release and consider this item at that time. To learn more about our issue management process and to have better expectation regarding different types of issues you can read our Triage Process.

@mkArtakMSFT mkArtakMSFT modified the milestones: Backlog, BlazorPlanning Nov 5, 2023
@ghost
Copy link

ghost commented Dec 21, 2023

Thanks for contacting us.

We're moving this issue to the .NET 9 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
Member

This is now supported by VS.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
affected-medium This issue impacts approximately half of our customers area-blazor Includes: Blazor, Razor Components enhancement This issue represents an ask for new feature or an enhancement to an existing one feature-blazor-tooling Blazor specific tooling requests Pillar: Dev Experience severity-minor This label is used by an internal tool
Projects
None yet
Milestone
.NET 9 Planning
Development

No branches or pull requests
10 participants
@pranavkm @SteveSandersonMS @captainsafia @danroth27 @javiercn @MackinnonBuck @TanayParikh @mkArtakMSFT @AniAchar @johnmagesh