SchemaPath outside project root doesn't work

[Yohandah]

Describe the bug
It is not possible to reference a schema that's outside of the project's root.

"schemaPath": "../backend/schema.graphql",

To Reproduce

I have a NestJS server and a frontend in Angular that consumes the GraphQL api with an Apollo Server. My frontend uses graphql-tag with gql'query MyQuery() { }' and the extension cannot autocomplete and says "unknown field" and the query is in red.

1. Create a backend and generate a schema.graphql
2. Create a frondend and a .graphqlconfig then try to reference your backend's schema

Expected behavior
We should be able to ../../ outside the project.

Additional context
It works when I open the folder with the two projects inside but I don't want to because then my IDE doesn't work properly since boths projects have different tslint, typescript version, prettier, etc

--folder
----frontend
----backend
------schema.graphql

[Leksat]

I met the same limitation and was able to workaround it with a symbolic link. Hacky, but works 🙂

[joelworsham]

Same issue. Probably a common pattern. Add support please?

[vepanimas]

@joelworsham Hi! As mentioned in issue #668, probably, this one will also be resolved. It would be great if you could give an EAP a try!

Schemas defined in parent directories should work in the upcoming 2023.3 release, you can try an already published EAP to check if the issue is solved for you.