Hi @icetomcat, that error usually comes from having a misconfigured or globally installed ESLint installation.
Can you better describe your dev environment?
Would be the best if you could open an issue on GitHub and follow the proposed template: https://github.com/quasarframework/quasar/issues
In other words, app extensions are a good place to put API related things, so developers don’t have to continually create the same wheel. 😉
Hmm, maybe it is a good idea to have first incarnation of QDataSource as an app extension afterall. Nevertheless, the support from “data consumer” components (QTable, QTree, QList etc.) in terms of something like hooks, events, etc would be needed also.
I’m not entirely convinced to this GraphQL thingy, but because this graphql is dynamic on the client side then maybe Quasar data components (QTable, QTree etc) would greatly benefit from such integration.