Are GraphQL queries supposed to trigger controller actions in Strapi v4?

[KadlinoBIT]

Hi,
I have copy-pasted a small update from one of the Strapi team-members regarding the way of resolving gql queries / mutations is in this topic:

GraphQL custom resolver in V4

Hello. I am trying to resolve a graphQL query. I want to share as much logic as possible between REST and graphQL, therefore I am trying to call a controller in my resolver. First question - is it a good idea to resolve a query / mutation using a controller? Or should I rather use a service? Second question - when I get the data from the controller, how does it need to be formatted before it’s returned in gQL response? I have tried following: 'use strict'; module.exports = { /** * An a…

Long story short, controllers should not be used to resolve gql queries as one of the goals for v4 was to decouple REST & GraphQL.