feat(useStrapiGraphQL): support for imported graphql files #249
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Types of changes
Description
Adds support for queries that are imported from a file. For instance, if someone used @rollup/plugin-graphql with Vite to import a GraphQL file, the imported file would be a
DocumentNode
and not the expected query by the Nuxt/Strapi module today. This feature adds support for those imported queries directly in the module without the need to transform the query first, like so:Since variables are defined on the query and can't be passed directly when using a file, an optional variables argument is added to the
useStrapiGraphQL
composable so that those arguments can be passed.This change relies on #248 (a fix for missing header on request). It also adds a dependency of "graphql" for conversion of given graphql document.
Checklist: