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 Issue Prevents Rebuild #73

Closed
FlorianRappl opened this issue Mar 4, 2022 · 0 comments
Closed

Scaffolding Issue Prevents Rebuild #73

FlorianRappl opened this issue Mar 4, 2022 · 0 comments
Labels
blazor-v3.2 Applies to .NET Core 3.1 blazor-v5 Applies to .NET 5.0 blazor-v6 Applies to .NET 6.0 bug Something isn't working
Milestone
v1

Comments

@FlorianRappl
Copy link
Collaborator

Similar to #59 we need to ensure that a failed scaffold (e.g., due to some missing dependency) does not prevent a scaffold in the future.

Right now when the initial scaffold fail (but still created the folder structure) a subsequent scaffold will not touch it. This is sub-optimal.

Ideally, we introduce a flag that also includes all used dependencies, allowing us to determine when we need to upgrade / re-scaffold etc.
@FlorianRappl FlorianRappl added the bug Something isn't working label Mar 4, 2022
@FlorianRappl FlorianRappl added this to the v1 milestone Mar 4, 2022
@FlorianRappl FlorianRappl added in-implementation Currently being implemented. blazor-v6 Applies to .NET 6.0 blazor-v5 Applies to .NET 5.0 blazor-v3.2 Applies to .NET Core 3.1 and removed in-implementation Currently being implemented. labels Mar 13, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
blazor-v3.2 Applies to .NET Core 3.1 blazor-v5 Applies to .NET 5.0 blazor-v6 Applies to .NET 6.0 bug Something isn't working
Projects
None yet
Milestone
v1
Development

No branches or pull requests
1 participant
@FlorianRappl