feat: add configurable JSON indentation - #218
Open
ChrisJr404 wants to merge 1 commit into
Open
Conversation
Add an `indent` configuration option that controls how many spaces are used per level when prettifying the input data and query results. It defaults to 4 spaces so existing behavior is unchanged, and can be set in the YAML config file, e.g. `indent: 2`. Smaller indentation makes deeply nested JSON easier to read by fitting more data on screen in both panes. Closes noahgorstein#188
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
1 participant
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.
This adds an
indentoption to the config file that controls how many spaces are used per level when prettifying the input data and query results, which addresses #188.The default stays at 4 spaces so nothing changes for existing users, but you can now drop it to
indent: 2(or any positive number) in.jqp.yaml. As the issue points out, tighter indentation makes deeply nested JSON easier to scan since more of it fits on screen in both panes.The value threads through the same way the theme does, from the config down into
utils.Prettify. A non-positive or unset value falls back to the 4-space default. I also updated the README and the settings schema, and added a few tests for the indenting logic since there weren't any covering it yet.