You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm not sure if this is a bit of a yak shave, but - in light of the intrinsic dependency that the Hotwire Turbo ecosystem has on ActionCable and the current workaround required, does it make to control the inclusion/exclusion of these libraries with this flag as well?
Actual behavior
I was attempting to reproduce the behavior reported in thoughtbot/administrate#2548, and realized that ActionCable is a soft dependency for the turbo-rails library. The Gemfile generator (at present) does not recognize the --ignore-action-cable flag when adding turbo-rails and stimulus-rails to the Gemfile.
System configuration
Rails version: 7.1.3.2
Ruby version: 3.2.2
The text was updated successfully, but these errors were encountered:
Now that Rails 8 alpha includes Turbo by default, this issue is becoming more apparent. I submitted a similar issue #51860 where the Rails app cannot boot in production if action cable is skipped. I don't know what the best solution would be, but I have mentioned @dbelling's suggestion as one of them.
Steps to reproduce
Expected behavior
I'm not sure if this is a bit of a yak shave, but - in light of the intrinsic dependency that the Hotwire Turbo ecosystem has on
ActionCable
and the current workaround required, does it make to control the inclusion/exclusion of these libraries with this flag as well?Actual behavior
I was attempting to reproduce the behavior reported in thoughtbot/administrate#2548, and realized that
ActionCable
is a soft dependency for theturbo-rails
library. The Gemfile generator (at present) does not recognize the--ignore-action-cable
flag when addingturbo-rails
andstimulus-rails
to the Gemfile.System configuration
Rails version:
7.1.3.2
Ruby version:
3.2.2
The text was updated successfully, but these errors were encountered: