df88a42e5f
* main: (21 commits) feat: action cable connection callbacks fix: action cable stream_test errors Adds test coverage for #attach method behaviour in activestorage Address QueryCacheTest#test_query_cache_does_not_allow_sql_key_mutation failure Fixes ActiveStorage proxy downloads of files over 5mb in S3-like storage services Fixes development Action Mailbox new mail form Squash commits Include the unexpected class in InvalidParameterKey message Support unbounded time ranges for PostgreSQL Fix CHANGELOG alignment [ci-skip] Add ability to ignore tables by regexp for SQL schema dumps Improve `rails s` error message when no server could be found. Fix MySQL warning when creating Active Record's test databases Add `--js` and --skip-javascript` options to `rails new` Fix parsing operator classes for index columns in PostgreSQL Fix rails test command to handle leading dot slash Document that url_for can take classes Don't change the encoding of frozen parameters Update working_with_javascript_in_rails.md Avoid query from calculations on contradictory relation ... |
||
---|---|---|
.. | ||
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: