-
Notifications
You must be signed in to change notification settings - Fork 368
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
Evaluate supporting baseline in dotnet new and template engine #4062
Comments
Some open questions for me to investigate:
|
Internal Usage:
External Usage:
All of the external usage feels very copy/pasted from our templates to me. This isn't surprising, given that we don't have a template-for-templates. I don't think that this functionality is very widely used at the moment. There is a potential use case for it as a solution to #3654, however. |
No change to this behavior in scope of #2191, the baseline option remains hidden. |
We should deprecate |
As it was agreed to deprecate baseline, we need to make all code that uses it obsolete. The action is purely refactoring, until obsolete code is agreed to be removed. Consider removing |
Currently template engine supports baseline: set of predefined input parameters that can be used when running or filtering templates.
dotnet new
supports--baseline
switch, but for now it is hidden.Evaluate do we need this feature enabled for .NET 7, keep it hidden as is or should we remove it.
The text was updated successfully, but these errors were encountered: