-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
Remove isChild from fastJsonNode #5184
Conversation
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.
Reviewed 1 of 1 files at r1.
Reviewable status: complete! all files reviewed, all discussions resolved (waiting on @animesh2049 and @martinmr)
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.
Reviewed 1 of 1 files at r1.
Reviewable status: complete! all files reviewed, all discussions resolved (waiting on @martinmr)
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.
Reviewed 1 of 1 files at r1.
Reviewable status: complete! all files reviewed, all discussions resolved (waiting on @martinmr)
While forming JSON response from Subgraph, we build one intermediate data structure called fastJsonNode tree. Each fastJsonNode has some fields which help correct encoding to JSON. isChild and list are also part of these fields. Currently isChild and list are used interchangeably and serve same purpose. This PR remove isChild for simplicity and better readability of the code. (cherry picked from commit 7ea3e4e)
While forming JSON response from Subgraph, we build one intermediate data structure called fastJsonNode tree. Each fastJsonNode has some fields which help correct encoding to JSON. isChild and list are also part of these fields. Currently isChild and list are used interchangeably and serve same purpose. This PR remove isChild for simplicity and better readability of the code.
While forming JSON response from Subgraph, we build one intermediate data structure called fastJsonNode tree. Each fastJsonNode has some fields which help correct encoding to JSON. isChild and list are also part of these fields. Currently isChild and list are used interchangeably and serve same purpose. This PR remove isChild for simplicity and better readability of the code.
While forming JSON response from Subgraph, we build one intermediate data structure called fastJsonNode tree. Each fastJsonNode has some fields which help correct encoding to JSON. isChild and list are also part of these fields. Currently isChild and list are used interchangeably and serve same purpose. This PR remove isChild for simplicity and better readability of the code.
While forming JSON response from
Subgraph
, we build one intermediate data structure calledfastJsonNode
tree. EachfastJsonNode
has some fields which help correct encoding to JSON.isChild
andlist
are also part of these fields.Currently
isChild
andlist
are used interchangeably and serve same purpose. This PR removeisChild
for simplicity and better readability of the code.This change is