You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Many editors with GraphQL plugins (PhpStorm, VS Code ) and GraphQL "playgrounds" allow you to give them a default .graphql schema file for auto-completion purposes. It's just a shortcut to having to rebuild the entire schema.
Since right now the Craft CMS GraphQL implementation doesn't build the full schema unless devMode is on, having such a default file would be useful:
The idea is that people could use the graphql console command to dump the schema, and then GraphiQL, various editors, etc. could then utilize it for auto-completion purposes without having to get the full schema back from Craft for the API.
In addition, support for graphql-config would be wonderful.
In addition to the 👍 I would also like to say this will be a huge help to our workflow since our headless CMS does not have devMode enabled. We still need to be able to test queries with the most up-to-date schema and I'd prefer not to have to fork this (now) huge database to a staging environment every time we update content models.
When we run headless we only spin up temporary review apps for each release but we don't need a long-running staging server in between releases because we don't need to worry about any frontend twig templates breaking.
Many editors with GraphQL plugins (PhpStorm, VS Code ) and GraphQL "playgrounds" allow you to give them a default
.graphql
schema file for auto-completion purposes. It's just a shortcut to having to rebuild the entire schema.Since right now the Craft CMS GraphQL implementation doesn't build the full schema unless
devMode
is on, having such a default file would be useful:The idea is that people could use the graphql console command to dump the schema, and then GraphiQL, various editors, etc. could then utilize it for auto-completion purposes without having to get the full schema back from Craft for the API.
In addition, support for graphql-config would be wonderful.
As @pauloelias said:
Related: #4834
The text was updated successfully, but these errors were encountered: