Should the CLI support user default setting values #9344
Comments
@KathleenDollard @nguerrera another application for |
In [alias]
dnc = !dotnet new console -n $2
etc. docs: https://git-scm.com/docs/git-config with usage: |
This sounds cool. Downsides? |
You can do aliases many ways. .gitconfig is a clever way to do it xplat. However having functionality core to the CLI would be more expected. Aliases are a way for devs to personalize their experience for their machines and tools, add shortcuts etc on top of the experience the tools give us out of the box. |
I was too brief. I meant, any downsides to adding the ability to do aliases in the dotnet CLI itself. I don't want to require any other tools for basic behavior. |
I'm biased because I've said that I've wanted this a lot, but I don't think there are downsides. |
Working with a Razor Pages app. Having to type the namespace value over and over when adding a new page to the application.
Solved with creating local variable
The Azure CLI offers user defaults once set the user does not have to specify them in the actual command at all.
It would suffice that the dotnet application should support this feature for things like
--framework
,--language
,--nuget-source
etc. without having to have the developer script specifically via bash, powershell or some other means.The text was updated successfully, but these errors were encountered: