chore(deps): update graphqlcodegenerator monorepo (major) #846
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.
This PR contains the following updates:
2.16.5
->5.0.0
2.2.3
->4.0.0
2.5.0
->3.0.0
2.8.8
->4.0.1
2.5.13
->4.0.1
3.3.7
->4.0.0
2.13.8
->4.0.1
Release Notes
dotansimha/graphql-code-generator (@graphql-codegen/cli)
v5.0.0
Compare Source
Major Changes
dd9c7e148
Thanks @valkum! - Make @parcel/watcher optionalPatch Changes
#9513
fdd19d24d
Thanks @cichelero! - Update yaml dependency to 2.3.1Updated dependencies [
bb1e0e96e
]:v4.0.1
Compare Source
Patch Changes
#9479
0aa444b5d
Thanks @gilgardosh! - dependencies updates:graphql-config@^5.0.2
↗︎ (from^5.0.1
, independencies
)#9479
0aa444b5d
Thanks @gilgardosh! - Update graphql-config to v^5.0.2v4.0.0
Compare Source
Major Changes
bb66c2a31
Thanks @n1ru4l! - Require Node.js>= 16
. Drop support for Node.js 14Patch Changes
#9449
4d9ea1a5a
Thanks @n1ru4l! - dependencies updates:graphql-config@^5.0.0
↗︎ (from^4.5.0
, independencies
)#9449
4d9ea1a5a
Thanks @n1ru4l! - dependencies updates:@graphql-tools/apollo-engine-loader@^8.0.0
↗︎ (from^7.3.6
, independencies
)@graphql-tools/code-file-loader@^8.0.0
↗︎ (from^7.3.17
, independencies
)@graphql-tools/git-loader@^8.0.0
↗︎ (from^7.2.13
, independencies
)@graphql-tools/github-loader@^8.0.0
↗︎ (from^7.3.28
, independencies
)@graphql-tools/graphql-file-loader@^8.0.0
↗︎ (from^7.5.0
, independencies
)@graphql-tools/json-file-loader@^8.0.0
↗︎ (from^7.4.1
, independencies
)@graphql-tools/load@^8.0.0
↗︎ (from^7.8.0
, independencies
)@graphql-tools/prisma-loader@^8.0.0
↗︎ (from^7.2.69
, independencies
)@graphql-tools/url-loader@^8.0.0
↗︎ (from^7.17.17
, independencies
)@graphql-tools/utils@^10.0.0
↗︎ (from^9.0.0
, independencies
)cosmiconfig@^8.1.3
↗︎ (from^7.0.0
, independencies
)graphql-config@^5.0.1
↗︎ (from^4.5.0
, independencies
)#9371
d431f426e
Thanks @Axxxx0n! - Fixed option ignoreNoDocuments when using graphql configs#9275
2a5da5894
Thanks @milesrichardson! - Trigger rebuilds in watch mode while respecting rules of precedence and negation, both in terms of global (top-level) config vs. local (per-output target) config, and in terms of watch patterns (higher priority) vs. documents/schemas (lower priority). This fixes an issue with overly-aggressive rebuilds during watch mode.Updated dependencies [
4d9ea1a5a
,4d9ea1a5a
,f46803a8c
,63827fabe
,bb66c2a31
]:v3.3.1
Compare Source
Patch Changes
#9267
183749346
Thanks @milesrichardson! - Fix watch mode to listen to longest common directory prefix of relevant files, rather than only files below the current working directory (fixes #9266).#9280
ca1d72c40
Thanks @saihaj! - fix the default output directory for init commandv3.3.0
Compare Source
Minor Changes
#9151
b7dacb21f
Thanks @'./user/schema.mappers#UserMapper',! - AddwatchPattern
config option forgenerates
sections.By default,
watch
mode automatically watches all GraphQL schema and document files. This means when a change is detected, Codegen CLI is run.A user may want to run Codegen CLI when non-schema and non-document files are changed. Each
generates
section now has awatchPattern
option to allow more file patterns to be added to the list of patterns to watch.In the example below, mappers are exported from
schema.mappers.ts
files. We want to re-run Codegen if the content of*.mappers.ts
files change because they change the generated types file. To solve this, we can add mapper file patterns to watch using the glob pattern used for schema and document files.Then, run Codegen CLI in
watch
mode:Now, updating
*.mappers.ts
files re-runs Codegen! 🎉Note:
watchPattern
is only used inwatch
mode i.e. running CLI with--watch
flag.Patch Changes
b7dacb21f
,f104619ac
]:v3.2.2
Compare Source
Patch Changes
#9086
a34cef35b
Thanks @beerose! - dependencies updates:graphql-config@^4.5.0
↗︎ (from^4.4.0
, independencies
)jiti@^1.17.1
↗︎ (todependencies
)cosmiconfig-typescript-loader@^4.3.0
↗︎ (fromdependencies
)ts-node@^10.9.1
↗︎ (fromdependencies
)#9086
a34cef35b
Thanks @beerose! - Supportcodegen.ts
in ESM projectsv3.2.1
Compare Source
Patch Changes
#9051
f7313f7ca
Thanks @saihaj! - dependencies updates:micromatch@^4.0.5
↗︎ (todependencies
)#9051
f7313f7ca
Thanks @saihaj! - only run generate for files that users have listed in config to avoid running this over every change that codegen is not supposed to executev3.2.0
Compare Source
Minor Changes
288ed0977
Thanks @saihaj! - use @parcel/watcher for improved watch functionalityPatch Changes
288ed0977
Thanks @saihaj! - dependencies updates:@parcel/watcher@^2.1.0
↗︎ (todependencies
)chokidar@^3.5.2
↗︎ (fromdependencies
)v3.1.0
Compare Source
Minor Changes
#8893
a118c307a
Thanks @n1ru4l! - It is no longer mandatory to declare an empty plugins array when using a preset#8723
a3309e63e
Thanks @kazekyo! - Introduce a new feature called DocumentTransform.DocumentTransform is a functionality that allows you to modify
documents
before they are processed by plugins. You can use functions passed to thedocumentTransforms
option to make changes to GraphQL documents.To use this feature, you can write
documentTransforms
as follows:For instance, to remove a
@localOnlyDirective
directive fromdocuments
, you can write the following code:DocumentTransform can also be specified by file name. You can create a custom file for a specific transformation and pass it to
documentTransforms
.Let's create the document transform as a file:
Then, you can specify the file name as follows:
Patch Changes
4c422ccf6
Thanks @renovate! - dependencies updates:@whatwg-node/fetch@^0.8.0
↗︎ (from^0.6.0
, independencies
)8206b268d
,8206b268d
,a118c307a
,a3309e63e
]:v3.0.0
Compare Source
Major Changes
fd0b0c813
Thanks @n1ru4l! - drop Node.js 12 supportPatch Changes
#8883
321d5112e
Thanks @Solo-steven! - Fix PluckConfig overwrite problem.Updated dependencies [
fc79b65d4
,fd0b0c813
]:dotansimha/graphql-code-generator (@graphql-codegen/introspection)
v4.0.0
Compare Source
Major Changes
bb66c2a31
Thanks @n1ru4l! - Require Node.js>= 16
. Drop support for Node.js 14Patch Changes
4d9ea1a5a
,4d9ea1a5a
,f46803a8c
,3848a2b73
,ba84a3a27
,63827fabe
,50471e651
,5aa95aa96
,ca02ad172
,e1dc75f3c
,bb66c2a31
,5950f5a68
,5aa95aa96
]:v3.0.1
Compare Source
Patch Changes
8206b268d
Thanks @renovate! - dependencies updates:tslib@~2.5.0
↗︎ (from~2.4.0
, independencies
)8206b268d
,8206b268d
,a118c307a
,6b6fe3cbc
,a3309e63e
]:v3.0.0
Compare Source
Major Changes
fd0b0c813
Thanks @n1ru4l! - drop Node.js 12 supportPatch Changes
fc79b65d4
,fd0b0c813
]:dotansimha/graphql-code-generator-community (@graphql-codegen/near-operation-file-preset)
v3.0.0
Compare Source
Major Changes
#414
02d487c8c
Thanks @saihaj! - accept skipDocumentsValidation config parameter
This is a breaking change since previous versions skips all documents validation and this could
raise validation errors while generating types.
#411
218778010
Thanks @saihaj! - Drop support for Node.js 12 and 14. Require Node.js
>= 16
Patch Changes
#411
218778010
Thanks @saihaj! - dependencies updates:
@graphql-tools/utils@^10.0.0
↗︎(from
^8.8.0
, independencies
)#422
ef0adf8c2
Thanks @renovate! - dependencies updates:
tslib@~2.6.0
↗︎ (from~2.4.0
, independencies
)#407
03655cc7c
Thanks @aboks! - Fix duplicate imports with inlineFragmentTypes:
combine
dotansimha/graphql-code-generator (@graphql-codegen/typescript)
v4.0.1
Compare Source
Patch Changes
#9497
2276708d0
Thanks @eddeee888! - Revert default ID scalar input type to stringWe changed the ID Scalar input type from
string
tostring | number
in the latest major version oftypescript
plugin. This causes issues for server plugins (e.g. typescript-resolvers) that depends ontypescript
plugin. This is because the scalar type needs to be manually inverted on setup which is confusing.Updated dependencies [
2276708d0
]:v4.0.0
Compare Source
Major Changes
#9375
ba84a3a27
Thanks @eddeee888! - Implement Scalars with input/output typesIn GraphQL, Scalar types can be different for client and server. For example, given the native GraphQL ID:
string
ornumber
in the inputstring
in its selection set (i.e output)string
in the resolver (GraphQL parsesstring
ornumber
received from the client tostring
)string
ornumber
(GraphQL serializes the value tostring
before sending it to the client )Currently, we represent every Scalar with only one type. This is what codegen generates as base type:
Then, this is used in both input and output type e.g.
This PR extends each Scalar to have input and output:
Then, each input/output GraphQL type can correctly refer to the correct input/output scalar type:
Note that for
typescript-resolvers
, the type of ID needs to be inverted. However, the referenced types in GraphQL input/output types should still work correctly:Config changes:
If correctly, wired up, the following will be generated:
BREAKING CHANGE: This changes Scalar types which could be referenced in other plugins. If you are a plugin maintainer and reference Scalar, please update your plugin to use the correct input/output types.
bb66c2a31
Thanks @n1ru4l! - Require Node.js>= 16
. Drop support for Node.js 14Minor Changes
#9196
3848a2b73
Thanks @beerose! - Add@defer
directive supportWhen a query includes a deferred fragment field, the server will return a partial response with the non-deferred fields first, followed by the remaining fields once they have been resolved.
Once start using the
@defer
directive in your queries, the generated code will automatically include support for the directive.The generated type for
GetUserQuery
will have information that the fragment is incremental, meaning it may not be available right away.Apart from generating code that includes support for the
@defer
directive, the Codegen also exports a utility function calledisFragmentReady
. You can use it to conditionally render components based on whether the data for a deferredfragment is available:
#9304
e1dc75f3c
Thanks @esfomeado! - Added support for disabling suffixes on Enums.Patch Changes
4d9ea1a5a
,4d9ea1a5a
,4d9ea1a5a
,f46803a8c
,3848a2b73
,ba84a3a27
,63827fabe
,50471e651
,5aa95aa96
,ca02ad172
,e1dc75f3c
,bb66c2a31
,5950f5a68
,5aa95aa96
]:v3.0.4
Compare Source
Patch Changes
386cf9044
,402cb8ac0
]:v3.0.3
Compare Source
Patch Changes
#9150
92d86b009
Thanks @rliljest! - Properly escape enum identifiers when enumsAsConst is usedUpdated dependencies [
e56790104
,b7dacb21f
,f104619ac
,acb647e4e
,9f4d9c5a4
]:v3.0.2
Compare Source
Patch Changes
ba0610bbd
,4b49f6fbe
,b343626c9
]:v3.0.1
Compare Source
Patch Changes
8206b268d
Thanks @renovate! - dependencies updates:tslib@~2.5.0
↗︎ (from~2.4.0
, independencies
)8206b268d
,8206b268d
,8206b268d
,a118c307a
,6b6fe3cbc
,a3309e63e
]:v3.0.0
Compare Source
Major Changes
fd0b0c813
Thanks @n1ru4l! - drop Node.js 12 supportPatch Changes
fc79b65d4
,fd0b0c813
]:dotansimha/graphql-code-generator (@graphql-codegen/typescript-operations)
v4.0.1
Compare Source
Patch Changes
#9497
2276708d0
Thanks @eddeee888! - Revert default ID scalar input type to stringWe changed the ID Scalar input type from
string
tostring | number
in the latest major version oftypescript
plugin. This causes issues for server plugins (e.g. typescript-resolvers) that depends ontypescript
plugin. This is because the scalar type needs to be manually inverted on setup which is confusing.Updated dependencies [
2276708d0
]:v4.0.0
Compare Source
Major Changes
#9375
ba84a3a27
Thanks @eddeee888! - Implement Scalars with input/output typesIn GraphQL, Scalar types can be different for client and server. For example, given the native GraphQL ID:
string
ornumber
in the inputstring
in its selection set (i.e output)string
in the resolver (GraphQL parsesstring
ornumber
received from the client tostring
)string
ornumber
(GraphQL serializes the value tostring
before sending it to the client )Currently, we represent every Scalar with only one type. This is what codegen generates as base type:
Then, this is used in both input and output type e.g.
This PR extends each Scalar to have input and output:
Then, each input/output GraphQL type can correctly refer to the correct input/output scalar type:
Note that for
typescript-resolvers
, the type of ID needs to be inverted. However, the referenced types in GraphQL input/output types should still work correctly:Config changes:
If correctly, wired up, the following will be generated:
BREAKING CHANGE: This changes Scalar types which could be referenced in other plugins. If you are a plugin maintainer and reference Scalar, please update your plugin to use the correct input/output types.
bb66c2a31
Thanks @n1ru4l! - Require Node.js>= 16
. Drop support for Node.js 14Minor Changes
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.
This PR has been generated by Mend Renovate. View repository job log here.