We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Operation system: OSX IDE name and version: Webstorm 2019.1 Plugin version: 2.2.0
I have 2 projects with different schemas, I expect that they will have different scope
Got errors like: There is already a schema defined [@3:1]
There is already a schema defined [@3:1]
.graphqlconfig
{ "projects": { "App": { "schemaPath": "./graphql/app/schema.graphql", "include": ["./graphql/app/*.graphql"] }, "Reporting": { "schemaPath": "./graphql/reporting/schema.graphql", "include": ["./graphql/reporting/*.graphql"] } }, "extensions": { "endpoints": { "App": { "url": "" }, "Reporting": { "url": "" } } } }
Getting errors in */schema.graphql
*/schema.graphql
The text was updated successfully, but these errors were encountered:
there is related issue #84 but i did not find solution there
Sorry, something went wrong.
Hi Ivan.
Thanks for using the plugin.
The configuration looks valid so I'll need a way to reproduce the issue to help you.
Can you attach a minimal example that reproduces the issue as a zip file?
Best regards, Jim.
Nothing actionable on this in its current state.
Please add a comment with minimal reproducing example and I'll take a look.
No branches or pull requests
Version and Environment Details
Operation system:
OSX
IDE name and version:
Webstorm 2019.1
Plugin version:
2.2.0
Expected Behaviour
I have 2 projects with different schemas, I expect that they will have different scope
Actual Behaviour
Got errors like:
There is already a schema defined [@3:1]
Steps to Reproduce / Link to Repo with Reproduction and Instructions
.graphqlconfig
Getting errors in
*/schema.graphql
The text was updated successfully, but these errors were encountered: