Add simpler support for GqlQueryParameters #899
Merged
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.
Note that this only populated a GqlQueryParameter with a Value, never a Cursor.
While we could add overloads for cursors, the parameter type would be ByteString...
which can also be converted to Value. So I'm basically betting that when you've got a
ByteString, you're more likely to want to use it as a Value parameter than as a Cursor
parameter.
Fixes #887