Implement _experimental_snapshot/2
#3165
Closed
Conversation
This file contains 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
myaaaaaaaaa
force-pushed
the
output
branch
7 times, most recently
from
c57f385
to
ff73a8e
Compare
myaaaaaaaaa
changed the title
_experimental_output/2_experimental_snapshot/2
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Enables writing to files from within jq scripts.
Resolves #3153
The scary name and lack of documentation should serve to inform users that its behavior is subject to breaking changes, and should therefore not be used in production scripts for the time being.
At the moment, this builtin performs a dry run by default. To actually write any data to disk, set the environment variable
JQ_ENABLE_SNAPSHOT=1. A proper sandboxing interface is outside the scope of this PR, please refer to the link below instead:--sandboxflag to prevent dynamic loading of other files/data. #3092I've renamed this builtin to
snapshot/2to highlight the fact that script execution is unaffected by the results of the file writing process (dry run, success, failure), allowing scripts that use it to remain constant and repeatable.This allows the language to maintain referential transparency even when interacting with the outside world.