parses and ignores type annotations in native operaton parameters when executing #130
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
hallettj
requested review from
codedmart,
daniel-chambers,
danieljharvey and
BenoitRanque
danieljharvey
approved these changes
Nov 25, 2024
…annotation-on-the-connector-side
hallettj
deleted the
jessehallett/eng-1366-handle-parameter-type-annotation-on-the-connector-side
branch
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.
With changes in the native query DX we can now have type annotations in native query pipelines, and in native mutation commands. For example,
[{ "$documents": [{ "__value": "{{ name | string! }}" }] }]The connector needs to be updated so that when executing it does not interpret type annotations as part of the parameter name.