search

basgren / railways

A plugin for RubyMine and IntelliJ IDEA Ultimate that adds a panel with routes of Ruby on Rails application.
MIT License
46 stars 18 forks source link

Routes window not visible in IDEA 2022.1 #54

Open PhitherekReborn opened 2 years ago

PhitherekReborn commented 2 years ago

Routes tool window is not visible and is not available to be opened from any menu since upgrading to 2022.1

PhitherekReborn commented 2 years ago

This happens when multiple Rails modules are configured

johntrandall commented 2 years ago

@PhitherekReborn I'm seeing the same issue in RubyMine 2022.1. I'm just not seeing the panel.

Can you provide more information? What exactly do you mean by "when multiple Rails modules are configured"?

PhitherekReborn commented 2 years ago

Hello, There is an option in IDEA to define multiple modules inside a project. For me the issue appears only on a project that has multiple modules configured (in this case one for each Gemfile present in the project), for projects with only a single module configured it doesn't happen.

johntrandall commented 2 years ago

Thanks for explaining @PhitherekReborn. Unfortunately, turning modules on or off doesn't seem to be a feature of RubyMine. There is no module configuration. If the plugin is installed - it's on. It sounds like this plugin needs updating to continue working as expected.

thinkAmi commented 2 years ago

I have the same issue in RubyMine 2022.1.3 and Railways 0.8.17.

In my case, when I tried the following steps in RubyMine with no plugins showing, the Railways plugin appeared on a panel that was not displayed.

  1. Preferences > Plugin, Uncheck the Railways plugin, and click Apply button. (and unload plugin)
  2. Check the Railways plugin, and click OK button. (and re-load plugin)
kfuchs commented 2 years ago

@thinkAmi this worked for Intellij as well. Thank you :)

neilabdev commented 1 year ago

This an issue for me, though reapplying the plugin each day works fine. +1

Francois-gaspard commented 1 year ago

I am also affected by this issue. But at least, the workaround above works for me.