-
Notifications
You must be signed in to change notification settings - Fork 480
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
Added json option to env command #800
Merged
Merged
Changes from 1 commit
Commits
Show all changes
21 commits
Select commit
Hold shift + click to select a range
995ac31
Added json option to env command
zaucy 9db5e95
Using HashMap and formatting
zaucy b664e8e
Added conflicts with for json option
zaucy a189d56
Merge remote-tracking branch 'origin/master' into feat/json-env-command
Schniz 098ac69
fix cargo clippy
Schniz ef34a2b
add env --json e2e test
Schniz 888340f
update commands.md
Schniz 27df8d7
add changeset
Schniz 1e64df0
Merge remote-tracking branch 'origin/master' into feat/json-env-command
Schniz 69fb2b0
change colors of logs in tests
Schniz 3261816
only if supported
Schniz 938daaf
don't remove the file
Schniz 782c528
retry
Schniz 508db34
debug with tmate
Schniz 2676f0b
use UTF8 encoding, and use .ps1 extension
Schniz 18425e2
use latest powershell
Schniz ba921bc
Add a debug environment
Schniz 8ed16a1
don't limit to actor or failure() on the job itself
Schniz 16764a7
debug
Schniz ff45bb4
wrong PowerShell node file
Schniz 456093f
fix expectation
Schniz File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.
We should probably make it broader, so
--output=json
is preferable.--output=json
conflicts with--shell=ANY
which can be declared with#[clap(conflicts_with = "shell")]
That being said,
--shell=...
is practically--output=...
, right? so maybe we can leverage--shell=
to be used as--shell=json
? Kinda ugly naming but does not break and does not introduce another API complexity?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.
Ah I didn't know about
conflicts_with
. Thanks!Haha I almost did
--shell=json
. Maybe deprecating--shell
and replace it with--output
? That reads well in my head.Then for compatbility sake just have
--shell
map to--output
? Is there an option for that inclap
?