-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Rename .keystone/types
to .keystone
and add graphql
export to .keystone
#7733
Conversation
🦋 Changeset detectedLatest commit: 112a8f8 The changes in this PR will be included in the next version bump. This PR includes changesets to release 16 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 |
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
This pull request is automatically built and testable in CodeSandbox. To see build info of the built libraries, click here or the icon next to each commit SHA. Latest deployment of this branch, based on commit 112a8f8:
|
graphql
export to .keystone/types
.keystone/types
to .keystone
and add graphql
export to .keystone
16a9f42
to
514e7bd
Compare
011f3d7
to
3236e70
Compare
3236e70
to
5370579
Compare
26e4ead
to
f2ca4d1
Compare
I don't think we want to do this at this time. That may change in the future, but for now I will close this pull request. |
This adds a
graphql
export to.keystone
(renamed from.keystone/types
because with thegraphql
export, it is no longer just types) that is the same as thegraphql
export from@keystone-6/core
but uses the specific generated context type for the project. This is important for #7575 since not using the specific context will be more painful but it also generally improves the experience of using graphql-ts for schema extensions and virtual fields.