This repository was archived by the owner on Sep 2, 2022. It is now read-only.
--MemoryOnlyJSON to avoid dropping JSON to disk (zipped in-memory) #39
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
… causing malformed JSON output due to addition of MemoryStream logic
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
1 participant
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.
Adds the option to use MemoryStreams to store the JSON, which are used as pseudo-files during the zipping process (
--MemoryOnlyJSON). This avoids needing to drop the JSON files to disk.Had to butcher some of the output code flow I'm afraid to wedge it in so understand if it doesn't get accepted as-is.