Ben Asher
Ben Asher
@profnandaa any chance you'll have time to look soon?
Would it be possible to do a release that adds logging behind a flag (verbose or an env flag)? I can yarn patch it, but it might be more helpful...
We ended up disabling the cache with `--no-cache` when doing local development, since our team was clearing the cache multiple times a day.
Are you sure? I would imagine this is where server implementations could break from the spec, but looking at [this spec](https://spec.graphql.org/October2021/#sec-Validating-Requests) (hopefully looking at the right version) (section 6.1.1), only...
Specifically this part makes me hopeful that servers really shouldn't do this: > If validation errors are known, they should be reported in the list of “errors” in the response...
FWIW, graphql-js's reference implementation seems to honor this: https://github.com/graphql/graphql-js/blob/e15c3ec4dc21d9fd1df34fe9798cadf3bf02c6ea/src/graphql.ts#L122
I see! Yeah in that case, I understand. I think my comment still stands. What you're getting from this package is a ValidationRule, which implies hook-ability into the graphql validation...
In any case, improvements to the API here might provide a good way to educate users on the tradeoffs
We're having the same issue, and we were previously on v8 + flat config
Okay so I think I figured this out. In v9 reportUnusedDisableDirectives has a new default, which is not false (maybe it's warn or something, but it emits messages). However, jest-runner-eslint...