fix(cli): always disable interactive mode in non-TTYs #6419
Conversation
This file contains hidden or 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
merceyz
reviewed
Jul 26, 2024
| const interactive = this.interactive ?? configuration.get(`preferInteractive`); | ||
| const interactive = configuration.isInteractive({ | ||
| interactive: this.interactive, | ||
| stdout: this.context.stdout, |
Member
There was a problem hiding this comment.
Isn't it stdin that has to be interactive?
3 tasks
3 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
What's the problem this PR addresses?
When
preferInteractiveis set totrue,yarn {add,up}are interactive even outside TTYs, which is unintended.Can be checked by running
yarn add lodash > foo.txtin our repository.How did you fix it?
Made it disable interactivity when
stdoutisn't a TTY (and added a newconfiguration.isInteractivehelper).Checklist