Read on Twitter
Going through @redwoodJS tutorial this afternoon: https://redwoodjs.com/tutorial/welcome-to-redwood
Will update this thread with findings
Will update this thread with findings
The Rails feels of the default home page are making me feel right at home 
Super opinionated so far, in a good way! Especially as someone who has been pretty far away from frontend work recently, this feels nice and fast
Holy crap, I haven't had the chance to play with @prisma since their GraphQL days, but these migrations are ridiculously cool https://github.com/xuorig/redwood-shop/tree/master/api/prisma/migrations/20200404162025-create-products
Wow ok, scaffolding a new product concept gives you a GraphQL API, a "service" file, and even scaffolded UI. Impressive. https://github.com/xuorig/redwood-shop/commit/d7d53dcc98d943373363f75c6c84bf1fdac6c118#diff-915836dbf89b330fc0b63180b0b014a3
I really like the service abstraction. Looks easy to modify and escape the default CRUD if needed. Something I still don't get is how the GraphQL resolution work. Looks like services / GraphQL schema are coupled in some way. Reading 
Ok back, Reading https://redwoodjs.com/tutorial/side-quest-how-redwood-works-with-data to figure out the relationship between services and GraphQL. It looks like top-level fields only are mapped to a service. I can't see anywhere how one would customize a resolver if needed. Might have to look at the source.
Ah yes ok, our Apps have direct access to the GraphQL server instance, which is "just" an ApolloServer object: https://github.com/xuorig/redwood-shop/blob/master/api/src/functions/graphql.js
`makeMergedSchema` is the redwood specific API here. I like it, easily composable at this point.
`makeMergedSchema` is the redwood specific API here. I like it, easily composable at this point.
