Revise how to disable eager loading app/channels

[fxn]

(This is the same as #513, which I closed by accident.)

Fixes #512.

[dorianmariecom]

Thanks @dhh <3

[dorianmariecom]

@dhh Can you release a new version? That would be awesome

[t27duck]

Until a new version is released, this is the workaround I've been using that seems to work out well enough...

config/application.rb:

require_relative "boot"

require "rails"
# Pick the frameworks you want:
require "active_model/railtie"
...
# require "action_cable/engine"
...

# Require the gems listed in Gemfile, including any gems
# you've limited to :test, :development, or :production.
Bundler.require(*Rails.groups)

# Hack as turbo-rails loads the constant from the eager load paths.
# Remove once a new version is released.
class Turbo::StreamsChannel; end unless defined?(ActionCable)

[bruno-]

@afcapel any chance you can release a new gem version with this fix? 🙏

This is currently breaking my app in production (I have to resort to workarounds) because I'm using mission_control-jobs which is using turbo.

Many thanks

[AxelTheGerman]

Would also appreciate a new release that includes this fix. That should also solve #587 - I was just looking into fixing that and then found the code that already fixed it is there and merged but not released.

Thank you!