Schema Diffing for Authorization

After briefly discussing this approach in GraphQL-spec (https://github.com/graphql/graphql-spec/issues/592) I realized that this should instead be added as best-practice and not necessarily be part of the spec. Since the initial RFC, I have also added this information in "graphql-rules", available here: (https://graphql-rules.com/rules/authorization-schema-diffing) {https://github.com/graphql-rules/graphql-rules/pull/13}

As of now graphql.org suggests a single method of authorization; however in practice I have had to implement a different approach to address various concerns which I have discussed in the links mentioned before.

The Schema diffing approach can be likened to an API Gateway implementation of authorization and has it's benefits; as such I suggest that we include this approach in the knowledge base so that it can be more widely used and discussed.

Examinez les recommandations existantes relatives à l’autorisation sur graphql.org ainsi que la règle graphql-rules liée, puis localisez le point d’entrée du contenu de la base de connaissances du site. La tâche est considérée comme terminée lorsque l’approche de comparaison des schémas est documentée comme bonne pratique aux côtés de la méthode existante et que sa justification est claire.

Rédigé par le modèle d'indexation à partir du texte de l'issue.