Clojurians Log v2

I'm still figuring out what to do with directives; we have them in the schema and validated, but I haven't quite figured out the right way to expose them to user code. Perhaps yet another key in the context.

Ideally, the internal If and Unless directives would be implemented the same as user-defined directives, but I don't see a good way to do that yet.

So, in theory, you could use directives to describe auth, but in practice, Lacinia doesn't quite let you.

@jvtrigueros Right, we have a structure akin the viewer, but some of our types have fields that are restricted. So there are fields that you as a client see, but not necessarily can access.

Thanks for the explanation, @hlship, looking forward to when you guys do figure it out!

About your original question, you can do a good deal of schema decoration by arguments to resolver literals, though you do need to roll your own conventions. Eg

{ :projects {:type :ProjectList :resolve [:resolvers/projects {:user/required-role :user.role/admin}]}}
}}}

...then you'd need to implement the resolver that checks for :user/required-role and returns either the right object or nil

That would be decoration on the server side then I’d assume? I was more looking at decorating fields in such a way that a client knows that asking for them is futile. E.g. lets say that you need to have Admin role to retrieve anyones credit card number (please don’t do this)