@pyrons_@saltyAom I've had a couple of executors I've wanted to build for a long time, one purely focused on performance, and one based on effect.js
I like the separation of execution and schema building, rather than having one library that does everything
@pyrons_@saltyAom So it's more about performance than API? Pothos isn't based on yoga, it just produces a standard GraphQL schema that would work with any executor that understands resolvers (and can also work with other execution models like grafast)
Pothos recently added some cool new stuff:
- New standard-schema validation plugin: https://t.co/PLe8haWIuy
- Grafast Plugin: https://t.co/7AXmCKZi1B
- LLM support in docs: https://t.co/xPhtjQmPDs
New Open Source Release: A Prisma, Pothos & GraphQL Server Template
Type-safe, stable, scalable.
This stack offers incredible Developer Experience to build awesome GraphQL backends.
GitHub: nkzw-tech/server-template
New version of the @DrizzleORM plugin is out now: https://t.co/E4E7v3c1pc
This version updates everything to use the new RQBv2 API from drizzle.
This release has lots of breaking changes, but things should be a lot more stable now!
Now that Pothos v4 has shipped smoothly, its time for @DrizzleORM!
I just published an early preview of the drizzle plugin: https://t.co/E4E7v3c1pc
You can see a full example of a drizzle based API here: https://t.co/tfKD7kpfaT
Try it out, and let me know what you think!
@andrewingram I think it would be easy to build something that handles the easy cases in a couple hours, but getting something that can be generalized to all the use cases people want would take some careful API design
@andrewingram Not that I am aware of. I've seen a few people looking for something like this, but I've never been sure how types would be mapped (numbers -> int/float, Date -> Date/DateTime, IDs are generally just strings in zod, etc).
@DrizzleORM@xiniha_1e88df This has been on my to-do list for too long! I just read over the new graphql extension, and there's definitely some pieces that will simplify building the Pothos plugin a lot! Hoping to have time to release Pothos 4.0 soon, and drizzle is the top priority after that
Athena Crisis always runs the latest versions of:
* React
* Relay
* Prisma
* graphql-pothos
* Vite
* TypeScript
* React Router
* framer-motion
* …and many more
Go tell your mom that you helped build a video game! Thanks to everyone for working on these technologies 🙇♂️
Just added a couple new features to the dataloader plugin. `loadableGroup` makes data-loading lists with `where-in` style queries easier, and the new `byPath` option allows loadable fields to use arguments in the load method
🧙🏾 Package feature of the week: prisma-generator-pothos-codegen
This generator by @cauenor provides a fast way to generate a fully customizable CRUD GraphQL API with @pothos_graphql from your Prisma schema.
Try it out and ⭐️ it on GitHub!
https://t.co/QKSBMsdsI7
@nikolasburk @nditah_sammy @ykdojo@apollographql@typegraphql If you end up using Pothos, I'm more than happy to answer questions! Pothos has a prisma plugin that makes some of the harder pieces of building a GraphQL API with prisma a lot easier and more efficient.
@MurmeltierS@bloberenober@DrizzleORM@elitasson@nhost Yeah, it's pretty similar, genql has some cool ideas. Aliases is the biggest missing piece as far as I know, but I also want a better story around default selections (they support __scalar: true, but I want more control at gen time)
@MurmeltierS@bloberenober@DrizzleORM@elitasson@nhost One of the big benefits is that you could convert things like a Date scalar back into a Date object on the client which many graphql clients struggle to do (since they don't actually know anything about your schema)
@MurmeltierS@bloberenober@DrizzleORM@elitasson@nhost A couple downsides: You need to have details about your full schema in the client, so you would want to generate a compact schema representation.
inline argument values aren't great, so you probably want to extract those out to variables when generating a query