Yeah. The unacknowledged assumption being made is that n-definition (much less of a mournful) is inherently a problem. The reality is that each layer of the sta

Yeah. The unacknowledged assumption being made is that n-definition (much less of a mournful) is inherently a problem. The reality is that each layer of the stack, the definition means a different thing even if the fields are the same _right now_. I’m an advocate of utilities to flatten the layers as an effort-saving measure, but as something to opt into, rather than out of. The layers must always be conceptually there. The reason I don’t like things like Hasura et al is because they flatten by default (your GraphQL server essentially becomes just an ORM for your database), and you’re made to do extra work if you don’t want that.