Right. People keep telling me that code-first is better but there is no way all those complex APIs are easier to use than just spitting out some JSON from an en

Right. People keep telling me that code-first is better but there is no way all those complex APIs are easier to use than just spitting out some JSON from an endpoint. Schema-first feels more manageable. I'm not going to say I haven't had to do that a _bit_ here, when I've got into quite advanced things. (e.g. sometimes you might want to dynamically provide the values from an enum, or write your own decorators, or you might want a custom top-level resolver.) It's built on the WebOnyx reference implementation, so there's some help out there. But it's amazing how much code I haven't had to write, and being the sort of person I am with difficulties controlling focus, I absolutely love the schema-first approach. It interacts well with Eloquent scopes, with the ordinary API gate system, with policies and validations. It's actually weird how good it is. You still have all the same issues you have with GraphQL generally (like limiting graph traversals to things a user is authorized to see), but you have so many tools.