b05603f6e4
Rails components version files are organized in a particular way. On one hand, ActionCable::VERSION is defined in action_cable/gem_version.rb, but that file does not follow Zeitwerk conventions, so we ignore it. Addtionally, action_cable/gem_version.rb defines ActionCable.gem_version, and we need to eager load it to have that method available for client code. On the other hand, there is also action_cable/version.rb, which loads action_cable/gem_version.rb. That file follows the conventions because by loading it, the expected constant gets defined as a side-effect, but it does so in an unusual indirect way. All in all, the setup that we had technically works, but setting an autoload for VERSION in ActionCable makes you think too much about the interactions between these two files and the autoloads triggered by the existing require_relative, which eager loads anyway. I believe this simplification is easier to understand. |
||
|---|---|---|
| .. | ||
| app | ||
| bin | ||
| lib | ||
| test | ||
| .babelrc | ||
| .eslintrc | ||
| .gitignore | ||
| actioncable.gemspec | ||
| CHANGELOG.md | ||
| karma.conf.js | ||
| MIT-LICENSE | ||
| package.json | ||
| Rakefile | ||
| README.md | ||
| rollup.config.js | ||
| rollup.config.test.js | ||
Action Cable – Integrated WebSockets for \Rails
Action Cable seamlessly integrates WebSockets with the rest of your \Rails application. It allows for real-time features to be written in Ruby in the same style and form as the rest of your \Rails application, while still being performant and scalable. It's a full-stack offering that provides both a client-side JavaScript framework and a server-side Ruby framework. You have access to your full domain model written with Active Record or your ORM of choice.
You can read more about Action Cable in the Action Cable Overview guide.
Support
API documentation is at:
Bug reports for the Ruby on \Rails project can be filed here:
Feature requests should be discussed on the rails-core mailing list here: