Is it a good idea to wrap the graphql queries through meteor methods? Why I would like to check such option is to prevent exposure of the queries to the client via isSimulation check and dynamic imports.
Is it a good idea to wrap the graphql queries through meteor methods? Why I would like to check such option is to prevent exposure of the queries to the client via isSimulation check and dynamic imports.