645239817d
I am trying to find a sweet spot here.
Personally, not quite satisfied by having lib/action_cable/zeitwerk.rb. At the
same time, trying to avoid too taking much space in lib/action_cable.rb.
This patch also moves
require_relative "action_cable/version"
within ActionCable. Why? In a project, I like that the entrypoint defines the
namespace. That is the main file for that namespace.
Then, files below have it already created, and reopen it.
I just find this deliberate order of execution to be natural, hierarchical,
matching the project structure.
|
||
|---|---|---|
| .. | ||
| 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: