I have backend type definitions:

i have autogenerated schema file:

how can I set that the schema file belongs to a different scope and that it shouldn't conflict with other files?

I am generating a schema.graphql file to be PRESENT in the project for adding code completion. How to specify that the graphql files in the /api/src folder are isolated from the rest of the project and should not conflict with it?
I'll explain easier:
-
I have two folders backend and frontend, graphql intersect in them (one is generated based on the other), how can I indicate that these are two different scopes so that the error is not highlighted?
Lol, solution:
We shoud create two .graphqlconfig files in two scopes:
/backend/.graphqlconfig
/frontend/.graphqlconfig
@MaxmaxmaximusAWS actually, do you need to generate a separate schema file if you have all type definitions in the same project? They should be used for completion without any additional steps.
@vepanimas no, I'm using a framework that generates a graphql schema based on PostgreSQL tables =) https://www.graphile.org/postgraphile/
SQL FIRST =) by the way, I recommend it to you, this is something incredible
@MaxmaxmaximusAWS oh, ok, I got it. That looks quite promising. I don't do web development anymore, but I will definitely look at this tool.
Most helpful comment
@MaxmaxmaximusAWS actually, do you need to generate a separate schema file if you have all type definitions in the same project? They should be used for completion without any additional steps.