Feat: Support initial indentation in json_dump output - #755
Open
maruixin-kls wants to merge 1 commit into
Open
maruixin-kls wants to merge 1 commit into
maruixin-kls wants to merge 1 commit into
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.
Checklist
masterbranchtoxsuccessfully in local environment (Note: Jansson uses CMake/Autotools, verified compilation locally)Description:
This PR addresses Issue #588.
Problem:
Previously,
json_dumpand related functions did not support an initial indentation level for the root element when using pretty-printing. The output always started at column 0, making it difficult to embed the JSON output into other indented structures (like C code generation or nested config files).Solution:
do_dumpinsrc/dump.c.depth == 0and if indentation flags are set.