Authorization in type field takes effect after the query

[Fainaru]

Hello, I would like to know how I can make the @Authorized in a type field act before the query, since for example I have some things that I want the users to see and others not, and that it works for each item in the array and column of this same one is very heavy since if I have 20 columns and 1000 rows I would use the Authorized function 20000 times, and if it were before I would only do it once

[MichalLytek]

We use on production the GraphQL Yoga solution:
https://the-guild.dev/graphql/envelop/plugins/use-generic-auth

AFAIR it's calculated from the query tree and evaluated before execution.

[Fainaru]

Thank you very much for answering and I did not understand well, are you telling me then that instead of using Authorized(), I should use use-generic-auth instead?

[Fainaru]

because with the authorized this is what happens to me

It gives me all that for the array and I only have it in the id, if I had it in all of them there would be more, that's why I'm talking about validating it before and not after, I don't know if it can be done or if I'm explaining myself correctly

[MichalLytek]

Yes, you should use other solution. The one built-in in TypeGraphQL is simple and basic, does not cover all needs.

[Fainaru]

and in the case of InputTypes, since authorization and using generic authentication doesn't work, could you use a custom class validator? For example, I have a "where", I want some to be able to access some parameters of the input and others not.