This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to master, this PR will be updated.
Releases
@eddeee888/gcg-typescript-resolver-files@0.5.0
Minor Changes
f7831c1: Use resolversNonOptionalTypename instead of nonOptionalTypename
This makes using abstract types simpler because we do not return __typename for all types, only for union members and interface implementing types.
This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to master, this PR will be updated.
Releases
@eddeee888/gcg-typescript-resolver-files@0.5.0
Minor Changes
f7831c1: Use resolversNonOptionalTypename instead of nonOptionalTypename
This makes using abstract types simpler because we do not return __typename for all types, only for union members and interface implementing types.
f7831c1: Add scalarsOverrides config option
Record<string, { resolver?: string; type?: string | { input: string; output: string } }>
(Default:{}
)Overrides scalars' resolver implementation, type or both.
Example:
BREAKING CHANGE:
typesPluginsConfig.scalars
can no longer be used. Please usescalarOverrides
instead.f7831c1: Use optionalResolveType=true because resolversNonOptionalTypename works
f7831c1: Add scalarsModule config option
string
orfalse
(Default:graphql-scalars
)Where Scalar implementation and codegen types come from. Use
false
to implement your own Scalars.If using an module that is not
graphql-scalars
, the module must export resolver implementation and codegen type the same waygraphql-scalars
does e.g.Patch Changes