js-graphql-intellij-plugin
js-graphql-intellij-plugin copied to clipboard
Unstable schema discovery in Unity project with Rider IDE
Version and Environment Details Rider 2022.3.2 Plugin version: 3.4.0
Describe the bug
when first create the .graphqlconfig file and execute it to generate schema.graphql file, GraphQL panel can discover the schema correctly and everything looks good when write queries.
When close the IDE and reopen it, the previous dicovered schema will be changed to 'Default project-wide schema', and all the types in the schema file will have 'Unknown field "xxx": The parent selection or operation does not resolve to a valid schema type'
errors in .graphql files
Here is the my configuration file:
I'm not sure if it's because of the special project structure of unity project. The file structure looks like this in Rider:
actually the path is ProjectName/Assets/..., Assets folder is not the project root.
the methods I tried to solve this:
- invalidate caches
- file association in Rider settings
- put .graphconfig and schema.graphql file under ProjectName/Assets/
- put all .graphconfig and .graphql files under ProjectName/Assets/GraphQL/
the first method doesn't work, and the last 3 ones only work temporarily: when reopen the IDE or sometimes even switch beteen unity engine and Rider or create a new .graphql file to write a new query, same errors will occur again
Hey! As a quick solution please try to click on your .graphqlconfig
and choose Tools > Start Index
![image](https://user-images.githubusercontent.com/10243762/221557593-94905ac4-1c48-4c9d-a3fd-9184446808e5.png)
Hey! As a quick solution please try to click on your
.graphqlconfig
and chooseTools > Start Index
![]()
Hiiii vepanimas, thx for replying. this definitely solves my problem; and for others for reference:
- click on
.graphqlconfig
and chooseTools > Start Index
- if there's still schema error: "A schema should have a 'query' operation defined", do the same thing with
schema.graphql
file (click on the generatedschema.graphql
file and chooseTools > Start Index
)
I'm glad that it helped! Though let's leave that issue as opened for now, perhaps we will be able to solve it somehow in the future.