-
Notifications
You must be signed in to change notification settings - Fork 42
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
Graphql integration #525
Graphql integration #525
Conversation
d91c253
to
0f2a179
Compare
f08502c
to
3c103a4
Compare
dad2621
to
c12870d
Compare
919aa2f
to
d04ddb7
Compare
d04ddb7
to
5dfbf0c
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.
Thanks for the updates, left one optional recommendation!
}; | ||
``` | ||
|
||
## Access your GraphQL resources information |
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.
Do you anticipate customers asking about this? Recommend removing this section.
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.
Right now adding the GraphQL integration will change strictly nothing for users as the web platform does not display the information yet.
The goal is to warn users that this is not usable yet in case they came across this package so they don't try it out and feel let down.
I can replace this by a warning at the top of the README if that makes the purpose clearer?
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.
@louiszawadzki If this is a feature that we plan on supporting in the future, an alert it might work better. Not sure if the alert div is supported in this repo, but this is what we usually add to highlight information in docs:
## Access your GraphQL resources information | |
<div class="alert alert-info">Adding the GraphQL integration does not change any existing features. The information is not surfaced on the Datadog platform.</div> |
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.
nice work!
})[0] || null | ||
); | ||
} catch (e) { | ||
// TODO: telemetry |
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.
minor: it is better to create a ticket straight away and add its number here
5dfbf0c
to
10af167
Compare
What does this PR do?
Add integration to collect GraphQL queries and mutations.
I've checked with proxies that the correct information was sent in the payloads.
Review checklist (to be filled by reviewers)