Adding Pipetools option to _not_ write JSON files #5
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.
Our internal tools heavily depend upon Pipetools. However, Pipetools by design writes JSON files into the current working directory (or writes to stdout). This results in higher-level tools not requiring the JSON files (using the JSON directly as object) dripping JSON files wherever executed.
This PR adds an option to
pipetools.get(...)
to not write files.