-
Notifications
You must be signed in to change notification settings - Fork 10.3k
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
Inconsistent casing of template parameters #40970
Comments
This isn't unique to gRPC template. All the web templates have e.g. |
Ah, so the inconsistency is this is missing from grpc's Lines 47 to 49 in 4966b6c
|
FWIW all the templates I have locally use --framework except for grpc. This is the full list of templates that have capitalized parameters, are some other managed here as well? :)
I got the full list using |
Triage: Should we make all these cases insensitive? @DamianEdwards |
@rafikiassumani-msft yeah I think that makes sense. |
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. |
gRPC is fixed (--Framework vs --framework) I've renamed this issue to be generic to other templates with parameters than need to be looked at. |
Is there an existing issue for this?
Describe the bug
Template for grpc uses Framwork, which becomes
--Framework
and-F
rather than--framework
and-f
that other templates use, e.g. console, mstest, winforms.https://github.com/dotnet/aspnetcore/blob/main/src/ProjectTemplates/Web.ProjectTemplates/content/GrpcService-CSharp/.template.config/template.json#L53
The settings are case-sensitive on purpose:
dotnet/templating#3237
dotnet/templating#3238
Expected Behavior
Please consider using,
-f
framework.Steps To Reproduce
Exceptions (if any)
No response
.NET Version
7.0.100-preview.2.22153.17
Anything else?
No response
The text was updated successfully, but these errors were encountered: