-
Notifications
You must be signed in to change notification settings - Fork 20
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
chore(graphql): add operation names and extract variables #611
Conversation
This works independently of cryostatio/cryostat#1202 , but that backend PR includes a parsed query caching enhancement that makes the separated query/variables better performing. Without that backend change this doesn't really do much in practical terms. |
571d692
to
99908d3
Compare
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.
Looks good and worked as expected! Just a question and logs seem to show any logging for requests. Oh nvm, just saw https://github.com/cryostatio/cryostat/pull/1214
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.
Looks good to me then!
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.
Looks good to me too :D
Related to cryostatio/cryostat#1201
See also:
Adding operation names makes it easier to search logs server-side for specific queries for debugging. Extracting variables
allows queries to be reused on the server as explained in links above, which allows query caching for better API performance.