Omit whitespace when generating JSON artefacts #4983
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.
I'm not sure why Linguist ships with "pretty"-printed JSON files (shock quotes used, because 2-space indents are NOT pretty). If whitespace is omitted, several megabytes are shaved off the (unpacked) JSON files:
These files aren't intended for human consumption, so I've no idea why they're being generated that way on purpose. If somebody does need to browse their contents, reformatting JSON is trivial to do in anything with a JavaScript engine attached:
Template removed as it doesn't apply.