-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
dotnet user-secrets edit
#46919
Comments
Sorry, didn't mean to use the @dotnet-policy-bot account to file this issue. Was still logged in as it :-/ |
Seems |
Tagging subscribers to this area: @dotnet/area-extensions-configuration |
@MiYanni the issue here is not complaining about the wrong result coming from the library I moved the issue back to SDK repo. You can move it to any other repo if SDK is not the right one for CLI. Thanks! |
Is your feature request related to a problem? Please describe.
Editing user secrets via
dotnet user-secret
isn't the most comfortable way. In many cases, I want to edit the underlying JSON file. In VS one can do that by right clicking the project and selecting Edit User Secrets. Having a way to do this from the CLI would be nice.Describe the solution you'd like
Git has a similar issue in their config system and it exposes a
git config --edit
command that launches the configuration file in the default editor.I know one can get the path via
dotnet user-secrets list -v
but that isn't as obvious as a top-level command likedotnet user-secret edit
.The text was updated successfully, but these errors were encountered: