Smarter watch

[jgoux]

Is your feature request related to a problem? Please describe.

Currently when using the --watch mode, every project/plugin is run, no matter the file that changed. I think it could be optimized.

Describe the solution you'd like

The most flexible solution would be to provide a watch glob to each generates block in the config so we can target specific files.

generates:
path/to/file.ts:
 config:
   avoidOptionals: true
 plugins:
   - typescript
   - typescript-operations
 watch: src/**/!(*.graphql).{ts,tsx}

I also think some plugin such as typescript-operations could be optimized and exit early (and silently) if there was no change detected in the edited file. For example when I edit a file containing no graphql operation (so no gql-tag use) I expect the plugin to do nothing in watch mode. Right now it's regenerating all the operations.
So internally graphql-codegen would need to pass only the edited file to the plugin during watch mode.

Describe alternatives you've considered

Right now I'm doing it manually by splitting my configuration into multiple projects and using chokidar-cli in my scripts :

{
  "scripts": {
        "graphql-codegen:dev": "concurrently \"yarn graphql-codegen:on-hasura-change\" \"yarn graphql-codegen:on-operations-change\" \"yarn graphql-codegen:on-schema-change\"",
    "graphql-codegen:on-hasura-change": "chokidar \"packages/server/hasura/**/*\" --command \"graphql-codegen --project get-schema\" --silent",
    "graphql-codegen:on-operations-change": "chokidar \"packages/client/src/**/!(*.graphql).{ts,tsx}\" --command \"graphql-codegen --project from-operations\" --silent",
    "graphql-codegen:on-schema-change": "chokidar \"./schema.graphql\" --command \"graphql-codegen --project from-schema\" --silent",
  }
}

Additional context

[dotansimha]

Totally agree here. We try to watch specific files by default (without the watch defined), but allow to add additional files in case something is missing. The fact that we eventually aggregate all files into a single list might limit us. I totally agree that this could be improved.

[charlypoly]

Note:
The way we currently check for file changes is not working if Prettier - or similar code formatter, making the watch mode obsolete.

Source: #2872 (comment)

[danielgwilson]

Also just ran into this issue—would be nice to have this supported as it's inefficient to introspect an API endpoint every time (vs. introspecting to local once)

Tried to use projects but not super clear

[eddeee888]

We now have watchPattern:

generates:
  path/to/file.ts:
  plugins:
   - typescript
  watchPattern: 'src/**/*.tsx'

Please let me know if it does not solve the issue. 🙂