Use fixed dynamic_graphql and up rust version to 1.86 #2020
+33
−72
Conversation
This file contains hidden or 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
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.
What changes were proposed in this pull request?
Set dynamic_graphql to our fork where an issue involving signed integers being parsed as unsigned integers was fixed.
Why are the changes needed?
Fixes all graphql signed integer fields not accepting negative numbers.
Does this PR introduce any user-facing change? If yes is this documented?
No
How was this patch tested?
Tested with an applyViews query in the playground.
Are there any further changes required?
If the fork is accepted to the main repository and a new version is released, we should set the source for dynamic_graphql back to the main cargo version.