3 ms·
This is very neat, and I've actually been planning on building something similar - just never got around to it. I wasn't aware of tql, though, so it's not unlik
by IceDane 4y ago
This is very neat, and I've actually been planning on building something similar - just never got around to it. I wasn't aware of tql, though, so it's not unlikely I would have just used that instead.
The only "downside" I can see is that all my projects are already set up to use graphql-codegen, and switching to this or tql would just not be worth the effort. This is because 1. it's really not that much of a hassle to run graphql-codegen on the side, since i'm already running other things on the side anyway 2. I'm also using graphql-codegen for other things, such as generating types for cache updates and such in urql.
I might give this a spin in a fresh project, though. But it probably won't let me drop the codegen dependency completely.