Clojurians Log v2

Good info. This is a minor thing, but @hlship for uploading files to a GraphQL, at my work we just arguments like "fileRef" (String), where it refers to a named part of a multipart request. So you would for example have 1 part that has the file contents, and one part that has the normal GraphQL JSON payload (query and variables). FWIW, this has worked fine for us.

In C#, making the request looks like this:

@hlship do you have some txt resource (blog, etc...) talking about "why REST do not make sense". I totally agree with you. the idea of "transfer state" always sound odd for me, because it's always a partial message. Do you have some txts resources (a blog or somethign like) about it?

@hlship great podcast. I learned a lot. I particularly like the idea of not using JSON for my own clients and having Lacinia use EDN. I didn’t think of that but have been wondering how to maintain namespace keys

I have a question: why did Walmart switch from interceptors to directives for authentication? I can understand for authorization (finer grained) but it seems like auth-n is simpler as an interceptor?

My guess: Directives are exposed in the GraphQL Schema metadata, interceptors aren't, so it helps make better client programs.

@isak that’s a good point. so a client knows that it needs to escalate privs when accessing specific roots/objects. @hlship is this correct?

for anyone following this thread, this article is very informative https://blog.logrocket.com/graphql-directives-are-underrated/

on this info, I guess Walmart auth directives are schema side only i.e. not exposed to client

Ah, I guess I was wrong. I was thinking "of course they are exposed", but no: https://github.com/graphql/graphql-spec/issues/300