-
Notifications
You must be signed in to change notification settings - Fork 210
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
Do not hide --output
Flag in help
#4656
base: main
Are you sure you want to change the base?
Conversation
update testdata
77c23d8
to
cac2a8d
Compare
Azure Dev CLI Install InstructionsInstall scriptsMacOS/Linux
bash:
pwsh:
WindowsPowerShell install
MSI install
Standalone Binary
MSI
Documentationlearn.microsoft.com documentationtitle: Azure Developer CLI reference
|
I believe that one of the reasons we decided to hide the @rajeshkamal5050 / @weikanglim to add any more context. here. |
@@ -7,6 +7,7 @@ Usage | |||
Flags | |||
-e, --environment string : The name of the environment to use. | |||
--force : Overwrite any existing files without prompting | |||
-o, --output string : The output format (the supported formats are none). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is a negative UX impact -- we're offering a flag that doesn't change the behavior of the command.
@wbreza I believe you are indeed quite right, and I would encourage some discussion on the issue before proceeding forward here. |
A plus one to the history here - another thing that we should be mindful of if/when we land this is the fact that we "none" here to mean "normal human readable output" but I expect almost anyone would think that The formatting stuff is one of the things that we built early on thinking we might use it in a more uniform and general way (similar to how It may make sense over time to shift the mindset from "every command results in an object which can be rendered in a bunch of different formats (like |
What if we make the Also, let's make azd to add the flag only when there is at least 2 formats supported and not when format
|
Fix issue #4075.
Commented out the
_ = f.MarkHidden(outputFlagName)
line in theAddOutputFlag
function to ensure the-o
flag is no longer hidden.The
-o
flag is now correctly listed in the command help, making it easier for users to discover and use it.@rajeshkamal5050 for notification.