chore(deps): update dependency @graphql-codegen/visitor-plugin-common to v7#13265
chore(deps): update dependency @graphql-codegen/visitor-plugin-common to v7#13265renovate[bot] wants to merge 1 commit into
Conversation
|
✅ Docs preview has no changesThe preview was not built because there were no changes. Build ID: 6865a43e394743aa1ced59d1 ✅ AI Style Review — No Changes DetectedNo MDX files were changed in this pull request. Review Log: View detailed log
|
commit: |
renovate
Bot
force-pushed
the
renovate/graphql-codegen-visitor-plugin-common-7.x
branch
2 times, most recently
from
6ef5fc9 to
93ac7f7
Compare
renovate
Bot
force-pushed
the
renovate/graphql-codegen-visitor-plugin-common-7.x
branch
2 times, most recently
from
bb26e21 to
8d6891f
Compare
renovate
Bot
force-pushed
the
renovate/graphql-codegen-visitor-plugin-common-7.x
branch
from
8d6891f to
884e6df
Compare
This PR contains the following updates:
^6.0.0→^6.0.0 || ^7.0.0Warning
Some dependencies could not be looked up. Check the Dependency Dashboard for more information.
Release Notes
dotansimha/graphql-code-generator (@graphql-codegen/visitor-plugin-common)
v7.1.1Compare Source
Patch Changes
6d37a7dThanks @eddeee888! - Fix _fragments to be protected instead of
private
v7.1.0Compare Source
Minor Changes
8707247Thanks @eddeee888! - Create
typedDocumentStringto supportTypedDocumentStringusage (common in Client-side plugins when documentMode=string)v7.0.4Compare Source
Patch Changes
446aef4Thanks @eddeee888! - Fix fragments not getting deduped when
documentMode=graphQLTag
v7.0.3Compare Source
Patch Changes
55a4742Thanks @eddeee888! - dependencies updates:
@graphql-codegen/plugin-helpers@workspace:^↗︎(from
^7.0.0, independencies)v7.0.2Compare Source
Patch Changes
a6a6786Thanks @ikusakov2! - skip conditional selection separation when
extractAllFieldsToTypesCompact is enabled
v7.0.1Compare Source
Patch Changes
5f035cbThanks @eddeee888! - Fix
constenum applyingtypesPrefixandtypesSuffixincorrectlyv7.0.0Compare Source
Major Changes
#10496
afaace6Thanks @eddeee888! - Fix nullable field optionality in operations
Previously, a nullable Result field is generated as optional (marked by
?TypeScript modifier)by default. This is not correct, because generally at runtime such field can only be
null, andnot
undefined(both missing from the object ORundefined). The only exceptions are when fieldsare deferred (using
@deferdirective) or marked as conditional (using@skipor@include).Now, a nullable Result field cannot be optional unless the exceptions are met. This also limits
avoidOptionalsto only target Variables input, since some users may want to force explicitnullwhen providing operation variables.#10496
afaace6Thanks @eddeee888! - BREAKING CHANGE: visitors' config option are
moved based on their use case
base-visitor
there
correctly sync the enum type names. This is moved to base visitor
base-visitor there.
Refactors
usages now. The types now extend base-visitor types. This is now consistent with
documents-visitor extending base-visitor
plugin parses configOne, then the types for configOne must be in that class, rather than in
base-documents-visitor
Note: These visitors are rolled up into one type for simplicity
base-visitorbase-documents-visitorandtypescript-operationsvisitorbase-types-visitorandtypescriptvisitorbase-resolvers-visitorandtypescript-resolversvisitor#10496
afaace6Thanks @eddeee888! - BREAKING CHANGE: make
unknowninstead ofanythe default custom scalar type#10496
afaace6Thanks @eddeee888! - BREAKING CHANGE: Update deps to latest, some
only support ESM
Node 20 support is dropped in this release. Node 22 comes with
require()support for ESM, whichmeans it's easier to integrate ES modules into applications. Therefore, it is safe to start using
ESM-only packages.
If you are a user, please upgrade to Node 22. If you are a lib maintainer and see ESM vs CJS
issues when running Jest tests, try using Vitest.
#10496
afaace6Thanks @eddeee888! - BREAKING CHANGE: Drop Node 20 support
#10496
afaace6Thanks @eddeee888! - BREAKING CHANGE:
@graphql-codegen/visitor-plugin-common'sbase-types-visitorno longer hasgetNodeCommentorbuildEnumValuesBlockmethod.#10496
afaace6Thanks @eddeee888! - BREAKING CHANGE: Operation plugin and Client
Preset no longer generates optional
__typenamefor result type__typenamshould not be in the request unless:Note: Apollo Client users can still use
nonOptionalTypename: trueandskipTypeNameForRoot: trueto ensure generated types match the runtime behaviour.#10496
afaace6Thanks @eddeee888! - BREAKING CHANGE: Remove unused utility types
from
typescriptplugin as they were previously used fortypescript-operationsplugin:MakeOptionalMakeMaybeMakeEmptyIncrementalBREAKING CHANGE: Remove
getRootTypeNamesfunction because it's available in@graphql-utils/toolsand not used anywhereMinor Changes
#10496
afaace6Thanks @eddeee888! - Add support for declarationKind for
typescript-operations
typeorinterfacetypebecause it's an alias e.g.Variables = Exact<{ something: type }>typeorinterfaceextractAllFieldsToTypes:trueorextractAllFieldsToTypesCompact:true, Resultsare used as type alias, so they are forced to be
type. There is a console warning for users.#10496
afaace6Thanks @eddeee888! - Add importSchemaTypesFrom support
#10496
afaace6Thanks @eddeee888! - Adding config option
extractAllFieldsToTypesCompact, which renders nested types names with field names only (without
types)
#10496
afaace6Thanks @eddeee888! - Add generateOperationTypes to
typescript-operations to allow omitting operation types such as Variables,
Query/Mutation/Subscription selection set, and Fragment types
#10496
afaace6Thanks @eddeee888! - Fixing 2 bugs: 1) including enums from
external fragments; 2) extractAllFieldsToTypesCompact does not create duplicates
Patch Changes
#10496
afaace6Thanks @eddeee888! - dependencies updates:
auto-bind@^5.0.0↗︎ (from~4.0.0, independencies)change-case-all@^2.1.0↗︎ (from1.0.15, independencies)#10496
afaace6Thanks @eddeee888! - dependencies updates:
auto-bind@^5.0.0↗︎ (from~4.0.0, independencies)change-case-all@^2.1.0↗︎ (from1.0.15, independencies)#10496
afaace6Thanks @eddeee888! - Improve
namespacedImportNameusability bysetting a default when
importSchemaTypesFromis set#10496
afaace6Thanks @eddeee888! - Add
printTypeScriptMaybeTypeto handleprinting TS types, as there are special cases like
anyandunknown#10496
afaace6Thanks @eddeee888! - Fix isNativeNamedType to handle types from
remote schemas correctly
Previously, we assumed that if a name type does note have
astNode, it is a native named typebecause it is not declared in user's schema.
However, this is a wrong assumption because remote schemas do not have
astNode. This causes alluser declared types are wrongly recognised as native types e.g. Input
#10496
afaace6Thanks @eddeee888! - Ensure Input and Variables use the same input
scalars default e.g.
IDcan takestring | number#10496
afaace6Thanks @eddeee888! - Fix namingConvention not being applied
consistently
#10496
afaace6Thanks @eddeee888! - Abstract how enum imports are generated into
visitor-plugin-common package
#10496
afaace6Thanks @eddeee888! - Fix namingConvention not being applied
consistently in imports, Variables, Input and Result
Updated dependencies
[
afaace6,afaace6,afaace6,afaace6]:v6.3.0Compare Source
Minor Changes
#10659
e65d303Thanks @ikusakov2! - Add support for
externalDocumentsexternalDocumentsdeclares GraphQL documents that will be read but will not have type filesgenerated for them. These documents are available to plugins for type resolution (e.g. fragment
types), but no output files will be generated based on them. Accepts the same formats as
documents.This config option is useful for monorepos where each project may want to generate types for its
own documents, but some may need to read shared fragments from across projects.
Patch Changes
9a66574Thanks @renovate! - dependencies updates:
tslib@^2.8.0↗︎ (from~2.6.0, independencies)[
9a66574,e65d303]:v6.2.4Compare Source
Patch Changes
cdf5dc5Thanks @ardatan! - dependencies updates:
@graphql-tools/relay-operation-optimizer@^7.1.1↗︎(from
^7.0.0, independencies)@graphql-tools/utils@^11.0.0↗︎(from
^10.0.0, independencies)[
cdf5dc5]:v6.2.3Compare Source
Patch Changes
6038634Thanks @Georgegriff! - fixed invalid extracted concrete type
name on shared interface
v6.2.2Compare Source
Patch Changes
f588d91Thanks @Georgegriff! - fix fragment type generation names
v6.2.1Compare Source
Patch Changes
b995ed1Thanks @Georgegriff! - Use parent type name on interface types
without fragments
v6.2.0Compare Source
Minor Changes
9e70bcbThanks @nickmessing! - add importExtension configuration option
Patch Changes
#10512
f821e8aThanks @realies! - fix: allow mappers to override root types (Query,
Mutation, Subscription)
Previously, mappers configured for root types were ignored because root types were checked before
mappers. This fix moves the mapper check before the root type check, allowing mappers to override
rootValueTypewhen configured.Updated dependencies
[
9e70bcb]:Configuration
📅 Schedule: (in timezone America/Los_Angeles)
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.