Repository navigation
Properly indent -json CLI output for readability - #1174
Open
jahedullah wants to merge 1 commit into
Open
jahedullah wants to merge 1 commit into
jahedullah wants to merge 1 commit into
Conversation
jahedullah
force-pushed
the
fix/pretty-print-json-cli-output
branch
from
September 1, 2026 19:46
26620f5 to
b68f280
Compare
Owner
|
@jahedullah Moreover, our Chrome extension depends on the JSON, and I would need first to test that the new formatting does not break anything there. In my opinion, the risks (i.e., breaking tests, breaking dependent projects) from this PR outweigh the benefits (i.e., JSON formatting). |
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.
Description:
Fixes the JSON format for -json CLI output by adding proper indentation, making it much more readable.
Testing:
Built a local Docker image and ran it against two commits; the output formatting was correct in both cases with proper indentation. The generated JSON file looks much better now.