Repository navigation
key:generate: send the warning to stderr - #12
Merged
Merged
Conversation
Contributor
Author
Bot reviewI ran Blocking
Non-blocking
|
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
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.
Problem: the unknown-option warning of key:generate went to stdout. So KEY=$(dox key:generate --show foo) held the warning and the key.
Fix: the warning goes to stderr. A test checks that stdout has only the key with --show. The other output in this command is not a warning: --show returns before the production check, and that check is shared with migration:fresh, so I left it.
Also: a registry test that key:generate foo passes validateArgs. Changelog line updated.