graphql-shield or fieldAuthorizePlugin, that is the question 🤔

We use graphql-shield and love it. It was super duper easy to set up and does the job for us.

I use it too but I want to give a try on the fieldAuthorizePlugin

choose whatever has the most stable support, none of them looks promising in this regard, but graphql-shield looks more safe to me

I also have a plugin

@Albert Gao why do you think that graphql-shield is safer than plugins ? the solutons seem pretty similar to me.

more stars, to this regard, so the repo is more likely to be maintain in a long term speaking, and apollo eco system has far more users than nexus eco system 🙂

Apollo community and nexus/prisma community are not separated. I don't thinks it's a popularity problem (as Nexus has 1.8k stars and graphql-shield 2.5k. Not "big" diff)

This is about one plugin vs a schema system. It’s actually quite big difference, at least my idea. Far More apollo users so more mrobust that plugin gonna get.

I think fieldAuthorizePlugin is more relevant as the

authorize

method is included inside the type definition. With graphql-shield you have to write a separated schema-like in order to define permissions. I think is less error prone to configure the whole type logic inside the type definition itself (it's the heart of code-first approach after all). But I like to confront my point of view with other devs (and certainly more experimented as I am)