Code-first GraphQL schemas with Pothos

[@holgerst3655]

Thanks for all your great explanations in your videos.

[@wayneswildworld]

You should probably show us how to do a mutation with input without a plugin first so we can know what the plugin is even doing. Also, you should probably include a git repository when you do these things.

[@notrab]

Thanks. Code can be found here graphql.wtf/episodes/60-code-first-graphql-with-pothos

[@patrikozafriko]

Been working with schema-first approach for years and after trying code-first with Prisma (which is using Pothos under the hood) approach I am terrified, the JS doc doesn't exist pretty much, if you are getting error from IDE, then it's so long and type intense to a point, where you can't even read that, error messages are strange and doesn't explain what's wrong, it's just a pain to work with, there are multiple magic helper functions that you are supposed to call to make stuff work, it's just really error prone. What's the point? Writing schema.graphql was always one of the smallest problems, even for complicated projects Schema-first can be also type safe with codegen, looks like Pothos is ruining the whole fun of GraphQL

[@notrab]

I’d have to agree. I’ve always been a fan of SDL-first but I do see the benefits of code-first.

[@chegevarra1036]

Can you show the final result what have you coding?

[@bugs181]

Not sure when it would be appropriate to use a code first approach unless it's a massive project that needs quality control. There's just far too much typing compared to schema-first approach. At that point, wouldn't it just be better to use codegen to build your schema from your code?

[@wayneswildworld]

from what I have heard people on the internet say, pothos is the best approach to make sure your schemas are typesafe I am a noob however and know nothing