feat(commons): make JSON pretty printing optional via indentOutput
#573
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.
Context
Currently, all allure-csharp integrations write JSON result files (
*-result.jsonand*-container.json) in a pretty-printed format, i.e., with indentation. While useful for debugging and manual inspection, this creates a substantial overhead to the files' size.The PR makes the compressed format the default. This results in approximately a 20-30% reduction in the size of JSON files (for our project with Allure NUnit examples, the reduction is 26%).
indentOutputThe PR introduces a new
indentOutputconfiguration property. If set totrue, the result files will be pretty-printed, resulting in the original behavior.Other changes
Allure.SpecFlow.TestsandAllure.Xunit.ExamplesindentOutputto true for all test projectsAllure.Net.Commons.Tests.FileSystemResultsWriterTestsAllure.Xunit.ExamplesChecklist