You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
incremental re-builds in codegen. It skips running any computations related to outputs when their documents, schemas didn’t change. Later on we could cache plugin outputs as well and run only those relevant. Even more interesting, we could calculate checksums and avoid generating unnecessary file even outside of watch mode
Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.
This PR includes no changesets
When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types
@kamilkisiela is this still being actively worked on? Would love to see this sort of improvement and wanted to see if there's anything I could do to assist.
The idea here was to also persist some kind of metadata file to build/skip things between executions of graphql-codegen command.
Ah nice, yeah that would be pretty useful - was starting to look into different options for speeding up the codegen by potentially building a smarter in-process watcher, which it looks like this is trying to do. We're using graphql-codegen (and several other graphql-tools) in the new v10 branch of Cypress: https://github.com/cypress-io/cypress/blob/10.0-release/graphql-codegen.yml and the codegen is a bit of a bottleneck when doing local development
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.
dotansimha
force-pushed
the
master
branch
2 times, most recently
from
ardatan
force-pushed
the
master
branch
2 times, most recently
from
Related: ardatan/graphql-tools#2816
incremental re-builds in codegen. It skips running any computations related to outputs when their documents, schemas didn’t change. Later on we could cache plugin outputs as well and run only those relevant. Even more interesting, we could calculate checksums and avoid generating unnecessary file even outside of watch mode
4s vs 0.4s
Nagranie.z.ekranu.2021-04-9.o.12.42.58.1.mov