@sjlutterbie Yep there’s been a preview release for a few months that should work with the newest graphql package release. Quite a few users have been asking for that.
🚀 Super excited about the idea of Preview Databases to complement your Preview Deployments of Vercel or Netlify, let us know what you think about it!
📺 And join us live for the Serverless Data Conference: https://t.co/UwTgpgFIRG
Excited to share another library from our work at Prisma. This time it comes from how we are building our GraphQL API on the new Prisma Cloud product. See 🧵 for details or just jump in right now at https://t.co/T2US8pMN1S. Enjoy! 🚀
Working on a lib to derive @nexusgql object type defs from Zod schemas, a great lib by @colinhacks.
✅.int() → Int
✅.optional() → strip !
✅.infer for Nexus type safety ❤️
✅ __typename
...
🤔 Not sure about GQL ID
🤔 Not sure about GQL descriptions
...more metadata needed!
A good week for Nexus Prisma with many minor fixes & features accumulating toward polished experience.
I wrote some thoughts on the next big feature of Nexus Prisma here https://t.co/7BgheemWDW if anyone is curious. The biggest API change since the initial release!
One reason I'm excited for [email protected] is the improved use of Nexus Prisma it allows. If you haven't seen the new Nexus Prisma check it out here https://t.co/RvaYmFegsl. It is in early preview and getting new features regularly!
[email protected] has just been cut ✨
→ Several relay plugin improvements
→ readonly enum members
→ t.field config with name
→ implement interfaces with extendType
→ plugin support for inputObjectType
And more! Check it out: https://t.co/nBa2477VyS
https://t.co/ECsdx2389s
I've been working on tracing a GraphQL API built with @prisma, @nexusgql, @fastifyjs & @opentelemetry💡
It took a lot of pain to get the instrumentation working, but it makes for a magical developer experience ✨
Feels like the holy grail of observability
👇
.@nexusgql has a lot going for it but I still think its plugin system is underrated ! It gives you a lot while staying really flexible and I not even talking about the @prisma plugin ! I took a look at it here in my last post https://t.co/XKmbtK5zCm
@itzz_me_5247@nikolasburk@Benoit_Boure@typegraphql Would you prefer a chaining API? Something else? If you can provide a gist converting some Nexus code to your ideal version that would be interesting for us! Not that we plan to change the "syntax" but its still worth seeing what others have in mind for the longer term.
🚨 JOB ALERT 🚨
We are building exciting things at Prisma that are going to need a great FE Dev with, mainly, these skills:
- Experience with Component Libraries
- A11y + Performance focus
As always, it's:
- A remote job
- In a Calm company
Apply here: https://t.co/MRNVqDofPp
Looking for @GraphQL backend people to would be willing to give @GraphMetrics a try 🙏
We support Golang (GQLGen) and JS (Apollo) servers for now and working on Python (Graphene) next. DM me!
Nexus is all about being able to stay in the toolchain you know. It takes time but the advantages of just having your programming language no “buts” or “ifs” keeps paying dividends as you build your API.
@mxstbr@TimSuchanek I’ve only tried Genql and like it a lot. Personally think staying in the TypeScript toolchain is a generally best. If you try this and aren’t happy would be curious. We continue to evolve our internal combo and if continues well may OSS it. Still early!
@Benoit_Boure Have you heard of @nexusgql or @TypeGraphQL? With their code-first approach to constructing a schema you can native JavaScript/TypeScript to declare your GraphQL types.
You can find examples using both libraries here: https://t.co/i5OtR9BGMJ