refactor(cli): output discipline — JSON purity, stderr status, standardized exit codes#281
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.
Summary
Third piece of the output-consistency work.
--output json|yaml|csvnow pipes cleanly (payload-only stdout), all progress/banners/warnings move to stderr, exit codes are standardized repo-wide, and API errors carry HTTP status + --debug hint.Changes
catch → fail(err)conversions (message + HTTP status + debug hint, exit 1)usageError()conversions — bad input exits 2 consistently (was DLP-only)parseAsync(async action rejections handled properly)Verification
dlp generate --output json | JSON.parseOK; missing-creds exit 1 with ✗ on stderr; 5 usage-error paths exit 2Checklist
Closes #269