[12.x] Let toPrettyJson()
accepts options
#56876
Merged
+65
−21
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
This PR enhances the
prettyJson
helper by introducing support for JSON options, giving developers more control over JSON encoding beyond the defaultJSON_PRETTY_PRINT
, see #56697.Motivation
Currently,
prettyJson
always forcesJSON_PRETTY_PRINT
, without a way to adjust encoding flags. This limits use cases such as:JSON_UNESCAPED_UNICODE
)JSON_UNESCAPED_SLASHES
)json_encode
options when neededBy making
options
configurable, developers can fine-tune the output according to their requirements.Changes
$options
parameter (default:none
) toprettyJson
.Example Usage
Testing
Related
N/A