Interest for a codegen blog post?
martinbonnin opened this issue · 9 comments
Hi everyone 👋
Martin from Apollo Kotlin here.
A question that's coming up quite often from our users is how come the codegen doesn't model classes after the GraphQL types but rather after the operations.
The reason is type safety of course (cannot access the fields you did not query) but given that GraphQL and a lot of other type systems are so similar, expecting the same shapes seems like a pretty reasonnable expectation to have.
I'd love to write a blog post explaining the different ways to look at codegen and the various tradeoffs there so that I could point users at.
Content would be cross-platform. Probably use TS for codeblocks examples but frame the content as cross platform enough so that it could apply to Swift/Kotlin developers as well.
Is that something that could belong to graphql.org? Any interest in this?
Absolutely; I'm sure we'd love to see this! I've come across the exact same confusion. Please go ahead, and let me know if you need any guidance or input.
cc @jorydotcom
My talk at GraphQL Conf is going to be about this same topic.
We could pair the talk as a companion to this post?
Draft here, comments welcome!
Any other feedbacks? What's the typical process here? Should I move the contents to https://github.com/graphql/graphql.github.io/tree/source/src/pages? Or something else?
Hey! Sorry, GraphQLConf ate all my time for the last month. Your blog post reads well; I've made a number of suggested edits for you to consider, some minor typo/grammar, and some more structural. Let me know what you think! Once accepted/rejected, we should indeed move the blog post into the website tree, like in #1731
No worries at all, hope GraphQL conf was a blast! One small comment remaining and I'll move that to a draft.
Thanks all for the feedbacks, I moved the post to GitHub here