The Guild LogoThe Guild Monogram

Search docs

Search icon

Products by The Guild

Products

Hive logoHive blurred logo

Hive

Schema Registry for your GraphQL Workflows

Docs

GraphQL Code Generator

Generate anything from GraphQL schema / operations!

Contact Us

TypeScript Vue Apollo Composition API

yarn add @graphql-codegen/typescript-vue-apollo
Usage Requirements#

In order to use this GraphQL Codegen plugin, please make sure that you have GraphQL operations (query / mutation / subscription and fragment) set as documents: ... in your codegen.yml.

Without loading your GraphQL operations (query, mutation, subscription and fragment), you won't see any change in the generated output.

Instead of using this plugin, it is recommended that you use the TypedDocumentNode plugin together with the Vue Apollo library.

This plugin generates

Config API Reference#

withCompositionFunctions

type: boolean default: true

Customized the output by enabling/disabling the generated Vue composition functions.

Usage Examples#

generates: path/to/file.ts: plugins: - typescript - typescript-operations - typescript-vue-apollo config: withCompositionFunctions: true
vueApolloComposableImportFrom

type: string default: (empty)

Usage Examples#

generates: path/to/file.ts: plugins: - typescript - typescript-operations - typescript-vue-apollo config: vueApolloComposableImportFrom: vue
vueCompositionApiImportFrom

type: string default: (empty)

Usage Examples#

generates: path/to/file.ts: plugins: - typescript - typescript-operations - typescript-vue-apollo config: vueCompositionApiImportFrom: vue
addDocBlocks

type: boolean default: true

Allows you to enable/disable the generation of docblocks in generated code. Some IDE's (like VSCode) add extra inline information with docblocks, you can disable this feature if your preferred IDE does not.

Usage Examples#

generates: path/to/file.ts: plugins: - typescript - typescript-operations - typescript-vue-apollo config: addDocBlocks: true
noGraphQLTag

type: boolean default: false

Deprecated. Changes the documentMode to documentNode.

gqlImport

type: string default: graphql-tag#gql

Customize from which module will gql be imported from. This is useful if you want to use modules other than graphql-tag, e.g. graphql.macro.

Usage Examples#

graphql.macro#
config: gqlImport: graphql.macro#gql
Gatsby#
config: gqlImport: gatsby#graphql
documentNodeImport

type: string default: graphql#DocumentNode

Customize from which module will DocumentNode be imported from. This is useful if you want to use modules other than graphql, e.g. @graphql-typed-document-node.

noExport

type: boolean default: false

Set this configuration to true if you wish to tell codegen to generate code with no export identifier.

dedupeOperationSuffix

type: boolean default: false

Set this configuration to true if you wish to make sure to remove duplicate operation name suffix.

omitOperationSuffix

type: boolean default: false

Set this configuration to true if you wish to disable auto add suffix of operation name, like Query, Mutation, Subscription, Fragment.

operationResultSuffix

type: string default: (empty)

Adds a suffix to generated operation result type names

documentVariablePrefix

type: string default: (empty)

Changes the GraphQL operations variables prefix.

documentVariableSuffix

type: string default: Document

Changes the GraphQL operations variables suffix.

fragmentVariablePrefix

type: string default: (empty)

Changes the GraphQL fragments variables prefix.

fragmentVariableSuffix

type: string default: FragmentDoc

Changes the GraphQL fragments variables suffix.

documentMode

type: DocumentMode default: graphQLTag

Declares how DocumentNode are created:

  • graphQLTag: graphql-tag or other modules (check gqlImport) will be used to generate document nodes. If this is used, document nodes are generated on client side i.e. the module used to generate this will be shipped to the client
  • documentNode: document nodes will be generated as objects when we generate the templates.
  • documentNodeImportFragments: Similar to documentNode except it imports external fragments instead of embedding them.
  • external: document nodes are imported from an external file. To be used with importDocumentNodeExternallyFrom

Note that some plugins (like typescript-graphql-request) also supports string for this parameter.

optimizeDocumentNode

type: boolean default: true

If you are using documentNode: documentMode | documentNodeImportFragments, you can set this to true to apply document optimizations for your GraphQL document. This will remove all "loc" and "description" fields from the compiled document, and will remove all empty arrays (such as directives, arguments and variableDefinitions).

importOperationTypesFrom

type: string default: (empty)

This config is used internally by presets, but you can use it manually to tell codegen to prefix all base types that it's using. This is useful if you wish to generate base types from typescript-operations plugin into a different file, and import it from there.

importDocumentNodeExternallyFrom

type: string default: (empty)

This config should be used if documentMode is external. This has 2 usage:

  • any string: This would be the path to import document nodes from. This can be used if we want to manually create the document nodes e.g. Use graphql-tag in a separate file and export the generated document
  • 'near-operation-file': This is a special mode that is intended to be used with near-operation-file preset to import document nodes from those files. If these files are .graphql files, we make use of webpack loader.

Usage Examples#

config: documentMode: external importDocumentNodeExternallyFrom: path/to/document-node-fileconfig: documentMode: external importDocumentNodeExternallyFrom: near-operation-file
pureMagicComment

type: boolean default: false

This config adds PURE magic comment to the static variables to enforce treeshaking for your bundler.

experimentalFragmentVariables

type: boolean default: false

If set to true, it will enable support for parsing variables on fragments.

strictScalars

type: boolean default: false

Makes scalars strict.

If scalars are found in the schema that are not defined in scalars an error will be thrown during codegen.

Usage Examples#

config: strictScalars: true
defaultScalarType

type: string default: any

Allows you to override the type that unknown scalars will have.

Usage Examples#

config: defaultScalarType: unknown
scalars

type: ScalarsMap

Extends or overrides the built-in scalars and custom GraphQL scalars to a custom type.

namingConvention

type: NamingConvention default: change-case-all#pascalCase

Allow you to override the naming convention of the output. You can either override all namings, or specify an object with specific custom naming convention per output. The format of the converter must be a valid module#method. Allowed values for specific output are: typeNames, enumValues. You can also use "keep" to keep all GraphQL names as-is. Additionally, you can set transformUnderscore to true if you want to override the default behavior, which is to preserve underscores.

Available case functions in change-case-all are camelCase, capitalCase, constantCase, dotCase, headerCase, noCase, paramCase, pascalCase, pathCase, sentenceCase, snakeCase, lowerCase, localeLowerCase, lowerCaseFirst, spongeCase, titleCase, upperCase, localeUpperCase and upperCaseFirst See more

typesPrefix

type: string default: (empty)

Prefixes all the generated types.

Usage Examples#

config: typesPrefix: I
typesSuffix

type: string default: (empty)

Suffixes all the generated types.

Usage Examples#

config: typesSuffix: I
skipTypename

type: boolean default: false

Does not add __typename to the generated types, unless it was specified in the selection set.

Usage Examples#

config: skipTypename: true
nonOptionalTypename

type: boolean default: false

Automatically adds __typename field to the generated types, even when they are not specified in the selection set, and makes it non-optional

Usage Examples#

config: nonOptionalTypename: true
useTypeImports

type: boolean default: false

Will use import type {} rather than import {} when importing only types. This gives compatibility with TypeScript's "importsNotUsedAsValues": "error" option

dedupeFragments

type: boolean default: false

Removes fragment duplicates for reducing data transfer. It is done by removing sub-fragments imports from fragment definition Instead - all of them are imported to the Operation node.

inlineFragmentTypes

type: InlineFragmentTypeOptions default: inline

Whether fragment types should be inlined into other operations. "inline" is the default behavior and will perform deep inlining fragment types within operation type definitions. "combine" is the previous behavior that uses fragment type references without inlining the types (and might cause issues with deeply nested fragment that uses list types).

Examples#

The examples below use Vue 2 with the (composition api plugin).

Queries#

Using the generated query code.

Basic query#

For the given input:

query Message { feed { id } }

We can use the generated code like this:

<template> <div> <div v-if="loading">Loading...</div> <div v-else>{{ result.feed.id }}</div> </div> </template> <script lang="ts"> import { defineComponent } from '@vue/composition-api' import { useMessageQuery } from '../generated/graphqlOperations' export default defineComponent({ setup() { const { result, loading } = useMessageQuery() return { result, loading } } }) </script>

Select a single property with useResult and add an error message#

For the given input:

query allAccounts { accounts { accountID givenName age } }

We can use the generated code with useResult like this:

<template> <div> <div v-if="loading">Loading...</div> <div v-else-if="error">Error: {{ error.message }}</div> <div v-else-if="allAccounts"> <div v-for="account in allAccounts" :key="account.accountID"> {{ account.accountID }} {{ account.givenName }} {{ account.age }} </div> </div> </div> </template> <script lang="ts"> import { defineComponent } from '@vue/composition-api' import { useResult } from '@vue/apollo-composable' import { useAllAccountsQuery } from '../generated/graphqlOperations' export default defineComponent({ setup() { const { result, loading, error } = useAllAccountsQuery() // Only select the property 'accounts' for use in the template const allAccounts = useResult(result, null, data => data.accounts) return { allAccounts, loading, error } } }) </script>

Use an options object#

Every useXxxxQuery can receive an options object to define query specific settings. To demonstrate the use of an options object we will try to only execute a query once a condition is met.

The ref isAuthenticated represents a boolean value that is set to true once the user successfully logged in to the app. To retrieve the user's application settings we can only execute the graphql query once the user is logged on (and the ref isAuthenticated is set to true). Setting this ref is done in another part of the app and is used as a simple example.

For the given input:

query { viewer { preference { language darkMode } } }

Within the options object is a property enabled that defines if a query is enabled or disabled. To only execute the query when isAuthenticated is true we set the property enabled equal to the ref isAuthenticated:

import { defineComponent, watchEffect } from '@vue/composition-api' import { useViewerQuery } from '../generated/graphqlOperations' import { isAuthenticated } from 'src/store/authentication' export default defineComponent({ setup(_, { root }) { // our imported ref: // const isAuthenticated = ref(false) const { result, loading, error } = useViewerQuery(() => ({ enabled: isAuthenticated.value, })) return { loading, error, result, } }, }) </script>

Package Details