-
Notifications
You must be signed in to change notification settings - Fork 51
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
refactor: Use int32
for proper gql scalar Int parsing
#1493
Conversation
Codecov Report
@@ Coverage Diff @@
## develop #1493 +/- ##
===========================================
+ Coverage 72.18% 72.27% +0.09%
===========================================
Files 185 185
Lines 18239 18239
===========================================
+ Hits 13165 13183 +18
+ Misses 4034 4021 -13
+ Partials 1040 1035 -5
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
EZPZ review. Sorry some explain stuff just merged today, you would have to resolve some conflicts, should be straightforward/easy, can also just do a bulk replace of all " int"
-> " int32"
on top of latest develop.
question: Could we perhaps benefit from setting the default branch to develop
for the graphql-go
fork: https://github.com/sourcenetwork/graphql-go
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👍
5deab1f
to
040a00d
Compare
…k#1493) Updates the graphql-go lib to [this](sourcenetwork/graphql-go@fe70855) update, which applies proper scalar Int parsing and coercing to return `int32` instead of `int`. This has *minor* downstream changes as you can see in this PR. Also had to update the explain tests @shahzadlone since it was using the filter types directly in the explain output which has now changed to `int32`
Relevant issue(s)
Resolves #938
Description
Updates the graphql-go lib to this update, which applies proper scalar Int parsing and coercing to return
int32
instead ofint
.This has minor downstream changes as you can see in this PR. Also had to update the explain tests @shahzadlone since it was using the filter types directly in the explain output which has now changed to
int32
Tasks
How has this been tested?
Manually + CI
Specify the platform(s) on which this was tested: