Repository navigation
Fix media generate --no-progress option registration - #12
Merged
Merged
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
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.
media generate --no-progresswas rejected as an unsupported option even though the generation handler already supports suppressing its stderr notice. Register the option on the native command so it is accepted and appears in help.Add an invocation-level regression test that verifies successful generation, an unchanged request payload, returned media and usage, and empty stderr. The existing progress test verifies that ordinary invocations still emit the notice.
Validation:
git diff --checkpassed.Dependency reinstallation, release packaging, npm installation, and live-server/plugin/player gates were not run for this focused command-registration change.