chore: remove automatic sql variable extraction #991
Merged
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
bbortt
force-pushed
the
issues/984-sql-action
branch
from
bb2f126 to
9ad9105
Compare
|
looks like I forgot to hit |
christophd
approved these changes
Sep 25, 2023
I know, didn't have time to look into it yet. possibly this evening! |
one must explicitly call `extract` using column- plut target-variable-names in order to extract data from the result into the current `TestContext`. BREAKING CHANGE: sql queries no longer automatically extract variables
bbortt
force-pushed
the
issues/984-sql-action
branch
from
9ad9105 to
44ba422
Compare
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.
one must explicitly call
extractusing column- plut target-variable-names in order to extract data from the result into the currentTestContext.BREAKING CHANGE: sql queries no longer automatically extract variables