- 16 12月, 2015 12 次提交
-
-
由 David Heinemeier Hansson 提交于
-
由 David Heinemeier Hansson 提交于
-
由 David Heinemeier Hansson 提交于
-
由 David Heinemeier Hansson 提交于
-
由 Rafael Mendonça França 提交于
-
由 Rafael Mendonça França 提交于
It should be configured through the railtie
-
由 Rafael Mendonça França 提交于
This will decouple Action Cable from Rails.
-
由 Rafael Mendonça França 提交于
That would make possible to use it with action cable configuration.
-
由 claudiob 提交于
[ci skip] Link to actioncable/README.md for more details
-
由 claudiob 提交于
[ci skip] Since Action Cable is getting integrated into rails/rails, the Travis badge for rails/actioncable is not needed anymore. Also following the standard of every other README to have `--` rather than `-` to separating the name of the library from its description.
-
由 Rafael Mendonça França 提交于
-
由 Rafael Mendonça França 提交于
Otherwise assets will not work
-
- 15 12月, 2015 28 次提交
-
-
由 David Heinemeier Hansson 提交于
Bring latest changes over from actioncable/master
-
由 Javan Makhmali 提交于
-
由 Eileen M. Uchitelle 提交于
remove extra spaces from deprecation message
-
由 David Heinemeier Hansson 提交于
-
由 yuuji.yaginuma 提交于
``` # before DEPRECATION WARNING: Time columns will become time zone aware in Rails 5.1. This still causes `String`s to be parsed as if they were in `Time.zone`, and `Time`s to be converted to `Time.zone`. To keep the old behavior, you must add the following to your initializer: config.active_record.time_zone_aware_types = [:datetime] To silence this deprecation warning, add the following: config.active_record.time_zone_aware_types << :time ``` ``` # after DEPRECATION WARNING: Time columns will become time zone aware in Rails 5.1. This still causes `String`s to be parsed as if they were in `Time.zone`, and `Time`s to be converted to `Time.zone`. To keep the old behavior, you must add the following to your initializer: config.active_record.time_zone_aware_types = [:datetime] To silence this deprecation warning, add the following: config.active_record.time_zone_aware_types << :time ```
-
由 Sean Griffin 提交于
We currently generate an unbounded number of prepared statements when `limit` or `offset` are called with a dynamic argument. This changes `LIMIT` and `OFFSET` to use bind params, eliminating the problem. `Type::Value#hash` needed to be implemented, as it turns out we busted the query cache if the type object used wasn't exactly the same object. This drops support for passing an `Arel::Nodes::SqlLiteral` to `limit`. Doing this relied on AR internals, and was never officially supported usage. Fixes #22250.
-
由 Sean Griffin 提交于
Some backends allow `LIMIT 1,2` as a shorthand for `LIMIT 1 OFFSET 2`. Supporting this in Active Record massively complicates using bind parameters for limit and offset, and it's trivially easy to build an invalid SQL query by also calling `offset` on the same `Relation`. This is a niche syntax that is only supported by a few adapters, and can be trivially worked around by calling offset explicitly.
-
由 Tim 提交于
Add boldface and bullets to make more readable. Make sentences declarative. Remove "you"s.
-
由 David Heinemeier Hansson 提交于
Controller-wide fragment cache key prefixes
-
由 Matthew Draper 提交于
Add migration versioning via Migration subclasses
-
由 Matthew Draper 提交于
Even though this means more things to change when we bump after a release, it's more important that our examples are directly copyable.
-
由 Matthew Draper 提交于
-
由 Matthew Draper 提交于
.. it also showed a deprecation warning, but we obviously needn't retain that.
-
由 Matthew Draper 提交于
-
由 Matthew Draper 提交于
Apart from specific versioning support, our tests should focus on the behaviour of whatever version they're accompanying, regardless of when they were written. Application code should *not* do this.
-
由 Matthew Draper 提交于
-
由 Matthew Draper 提交于
If we use a real version, at best that'll be an onerous update required for each release; at worst, it will encourage users to write new migrations against an older version than they're using. The other option would be to leave these bare, without any version specifier. But as that's just a variant spelling of "4.2", it would seem to raise the same concerns as above.
-
由 Matthew Draper 提交于
-
由 Matthew Draper 提交于
-
由 Sam Stephenson 提交于
-
由 Rafael Mendonça França 提交于
-
由 Rafael Mendonça França 提交于
-
由 Rafael Mendonça França 提交于
Travis still don't have a updated version
-
由 Sam Stephenson 提交于
Introduced in e56c6354, `CacheHelper#fragment_cache_key` is a duplicate of `ActionController::Caching::Fragments#fragment_cache_key`. We now require the view to provide this method on its own (as with `view_cache_dependencies`); `ActionController::Caching::Fragments` exports its version as a `helper_method`.
-
由 Rafael Mendonça França 提交于
-
由 Rafael Mendonça França 提交于
-
由 Rafael Mendonça França 提交于
We don't have isolation tests for it yet.
-
由 Rafael Mendonça França 提交于
The application can have more than one ApplicationController and we want Action Cable helpers in all controllers and their views so we should hook in the same place that others helpers.
-