Rename graphql export to g

[emmatown]

This renames the graphql export to g for two reasons:

• More concise reading/writing schemas
• To avoid conflicts with exports named graphql from libraries such as Relay, GraphQL Code Generator and gql.tada that use the variable name graphql to declare GraphQL operations

The graphql export still exists but is now deprecated and may be removed in a future release.

To quickly update usages of the graphql export in your project to use g:

1. Navigate to node_modules/@keystone-6/core/dist/declarations/src/types/schema/legacy-alias.d.ts in your editor ("Go to Definition" will not take you to the correct file)
2. Use "Rename Symbol" to rename graphql to g, this will update usages of graphql to g
3. Change this deprecated alias back from g to graphql (avoid using "Rename Symbol" again because you want to preserve the updates you made in step 2)

---

• Related graphql-ts PR: Rename graphql export to g Thinkmill/graphql-ts#19

[socket-security]

Updated dependencies detected. Learn more about Socket for GitHub ↗︎

Package	New capabilities	Transitives	Size	Publisher
npm/@graphql-ts/[email protected] 🔁 npm/@graphql-ts/[email protected]	None	0	103 kB	thinkmill-release-bot
npm/@graphql-ts/[email protected] 🔁 npm/@graphql-ts/[email protected]	None	0	203 kB	thinkmill-release-bot

View full report↗︎

[emmatown]

Note that this changeset has major changes but the @keystone-6/core changeset is only a minor since it's not breaking to add the new name and keep the old one around but using the new name is breaking since people must update @keystone-6/core otherwise these packages will not work. While this would be easily avoidable by using the old version, I don't think that complexity is worth it since people will already be forced to use all the new versions together because of the changes for @keystar/ui.

[emmatown]

If you're curious why I'm using this weird syntax, see the latter part of the PR description of Thinkmill/graphql-ts#19