Skip to content
New issue

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

Rider: plugin configuration doesn't work in Rider 2023.1 #659

Closed
gerwim opened this issue Apr 23, 2023 · 6 comments
Closed

Rider: plugin configuration doesn't work in Rider 2023.1 #659

gerwim opened this issue Apr 23, 2023 · 6 comments

Comments

@gerwim
Copy link

gerwim commented Apr 23, 2023

Describe the bug
The GraphQL plugin does not work on Rider. The schema is not discovered. When I open the same project in WebStorm, the schema is discovered.

I've tested this both on my Windows machine as my Mac machine, same results.

To Reproduce
Link to Repo with Reproduction or Steps to Reproduce:

  1. Clone https://github.com/gerwim/intellij-graphql-plugin-issue
  2. Open the repo in both Rider and WebStorm
  3. Open the GraphQL plugin tab
  4. Look at the schema discovery summary

Expected behavior
Both Rider and WebStorm should show the same results.

Screenshots
Rider:
image
WebStorm:
image

Version and Environment Details
Operation system: Windows and Mac
IDE name and version: Rider and WebStorm 2023.1
Plugin version: 4.0.0

@gerwim gerwim changed the title Rider: plugin does not work Rider: 4.0.0 of the plugin does not work Apr 23, 2023
@gerwim gerwim changed the title Rider: 4.0.0 of the plugin does not work [V4] Rider: plugin does not work Apr 23, 2023
@vepanimas
Copy link
Collaborator

@gerwim Hi! Probably, it's the same issue as #647. If so, it could happen before 4.0.0. Please, try to apply actions from the #647 (comment), did it help?

@gerwim
Copy link
Author

gerwim commented Apr 23, 2023

@vepanimas Thanks for your quick reply. It does not seem to help. Index is by default enabled on both files. If index is stopped, it's also affixed by "no index" -- and there are no files having that indication. All files are indexed.

BUT: when I disable the index on the graphql.config.yml file, the schema is discovered (but the endpoint went missing). I noticed it also changes to the "Default project-wide schema". I made sure to close WebStorm, invalidated the caches and deleted the .idea folder to make sure the data was not generated from the working plugin.

Screenshot with index disabled:
image

Screenshot with index enabled:
image

@vepanimas
Copy link
Collaborator

vepanimas commented Apr 23, 2023

@gerwim Could you please share the config?

It's clear from the first screenshot that the plugin couldn't find a configuration file and used a default global scope. However, even with a configuration file on the second screenshot, it can't locate the schema file for some reason.

@gerwim
Copy link
Author

gerwim commented Apr 23, 2023

@vepanimas What config are you looking for? I've shared the repo here: https://github.com/gerwim/intellij-graphql-plugin-issue/tree/master/ConsoleApp1

The shared project is a default console application created with Rider (hence the other files). I just used a public Pokemon GraphQL API (as I needed a public GraphQL API) -- I've tested with others too. When you open the project with WebStorm (or I suppose any other IntelliJ IDE) the plugin will (probably) work (I've only tested with WebStorm).

@vepanimas
Copy link
Collaborator

@gerwim, I believe I have found the reason for the issue. It seems to be specific to Rider 2023.1 only. With Rider 2022.3, the latest GraphQL plugin will work as expected. If you decide to downgrade Rider to 2022.3, make sure to reinstall the GraphQL plugin to use the specific backward-compatible version 4.0.0-222.

@vepanimas vepanimas changed the title [V4] Rider: plugin does not work Rider: plugin configuration doesn't work in Rider 2023.1 Apr 23, 2023
@vepanimas vepanimas added this to the 4.0.1 milestone Apr 23, 2023
@gerwim
Copy link
Author

gerwim commented Apr 23, 2023

@vepanimas Thank you very much for your time into this plugin and the time spent on investigating this issue. I need 2023.1 for a different reason so I installed 3.4.0 of the plugin (although schema retrieval doesn't work with 2023.1 and 3.4.0, I have a workaround for that).

Thanks again and I'll be awaiting your 4.0.1 release ;-)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants