Population after a custom graphql resolver, what does it?

Hi @Silvere_Letellier currently the auto population is too much and should (will) be removed in graphql queries so the data gets fetched only if the relations is queried.

The relation resolvers ignore the pre populated data in most cases because it might be missing informations (components inside the relation for example) so it fetches the relations even if you might think it is populated.

We will remove the pre population soon so the performance get a nice improvement :slight_smile:

1 Like