Axel Hultman

I'm also affected by this issue. Adds a need for a lot workaround that takes away a lot of the "magic" of working with graphql.

@0legg mind sharing how you did that?

@ictgtvt Do you know if it causes any issues for the facebook share preview or something similar? We're getting the same issue in our setup with lazysizes and bugsnag but...

```sh /usr/local/bin/node ./node_modules/vitest/vitest.mjs [ProjectRootPath] [vitest.commandLine] [ProjectRootPath]/apps/Somepackage/src/utils/__tests__/sometest.test.ts --api.port 64217 --api.host 127.0.0.1 DEV v0.28.5 [ProjectRootPath] API started at http://127.0.0.1:64217 ❯ packages/testing/__tests__/sometest.test.ts (0 test) ❯ apps/Somepackage/src/utils/__tests__/some-other-test.test.ts (0 test) ⎯⎯⎯⎯⎯⎯ Failed Suites 2 ⎯⎯⎯⎯⎯⎯⎯...

Anyone have a workaround for this? Working with generated types from the graphql is such a mess. Have you made workarounds in your scripts (to not follow the schema...) or...

How are you guys handing this in your applications? Huge headache for me

Completely agree with @bitfield, it really is one of those where it is really hard to go back once you got used to having it so immediate

Any updates regarding the roadmap on this? User expectations seem to be moving in this direction, both from devs and end users perspective