-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
fix: use gqlTagName
in the autogenerated example
#8995
fix: use gqlTagName
in the autogenerated example
#8995
Conversation
🦋 Changeset detectedLatest commit: 35e8b9e The changes in this PR will be included in the next version bump. This PR includes changesets to release 2 packages
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
@charpeni Thank you! Let us know when this is ready for review! |
@charpeni Can you please rebase upon the origin/master branch and then run |
dc93e61
to
d4df842
Compare
Pull request rebased upon |
@charpeni Don't forget to run |
@n1ru4l yes, I ran |
d4df842
to
35e8b9e
Compare
Ah, sorry! While working on another pull request, I just realized I was running |
Description
I noticed that the example generated wasn't using
gqlTagName
, and therefore the example saidgql
, but the recent version switched tographql
, and it got me confused for a second. I believe we probably want to leveragegqlTagName
for the example and the other places already relying on it.Type of change
Screenshots/Sandbox (if appropriate/relevant):
See updated snapshots and examples.
How Has This Been Tested?
yarn generate:examples
Checklist: