Introduce FLEXMEASURES_JSON_COMPACT setting #1090
Merged
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
Happening in a move to deprecate JSONIFY_PRETTYPRINT_REGULAR.
We saw this deprecation warning in our server logs a lot, so it's good to move on from it.
The new setting is so we can still control it (i.e. in production you might want to read nicely).
Per default, the setting is
True
as it saves on IO volume. It is onlyFalse
for development. Should it also beFalse
during testing?How to test
In a development environment, the default should be to not compact the JSON:
We can enforce compact JSON:
And the other way around:
Remember to unset this in your bash session: