Clojurians Log v2

Well, I can’t speak for your schema, but what we tend to do is to design connection filters on what users like to filter on and design return types on the shapes that may produce, but I haven’t had cases yet where those filters directly map to the types that may be returned.

hey there, quick Lacinia question if folks have a moment. i’m wondering if it’s possible to replace the root resolver, such that there is a single resolver for the whole query. i’ve tried adding a :resolve keyword to the :Query object, but it doesn’t get executed

Why would you want that over a resolver per field on the query root?

trying to model some specific behavior. it’s easy enough to just nest it down one level as a field resolver but i was just curious