- 11 10月, 2015 4 次提交
-
-
由 amitkumarsuroliya 提交于
-
由 amitkumarsuroliya 提交于
Improved `KeyError` messages on bang version, since commit https://github.com/rails/rails/commit/e768c519fb6015e00961702a5165c6dab548a954 bang version produces `KeyError` [ci skip]
-
由 Rafael Mendonça França 提交于
This reverts commit efbd62f0. Right now Eastern Time zone is on daylight saving, so the output in the documentation is different but this doesn't mean that it is wrong. Daylight savings only happen in 3 months in a year so it is better to use the normal time zone in the documentation.
-
由 amitkumarsuroliya 提交于
-
- 09 10月, 2015 1 次提交
- 08 10月, 2015 1 次提交
-
-
由 amitkumarsuroliya 提交于
`A UNIQUE` we pronounce URL as 'yu-ni-k’. We use this everywhere. So, be consistent with it.
-
- 07 10月, 2015 1 次提交
-
-
由 Ronak Jangir 提交于
-
- 04 10月, 2015 10 次提交
-
-
由 Vijay Dev 提交于
-
由 Jeremy Daer 提交于
Introduce `Headers#add`. Move `Response#add_header` upstream.
-
由 Jeremy Daer 提交于
* Introduce `ActionDispatch::Http::Headers#add` to add a value to a multivalued header. * Move `Response#add_header` upstream: https://github.com/rack/rack/pull/957 * Match upstream `Response#have_header?` -> `#has_header?` name change.
-
由 Jeremy Daer 提交于
-
由 Jeremy Daer 提交于
YAGNI concurrent-ruby master branch now that 1.0.0.pre3 is released with fixes for warnings and circular require
-
由 Aaron Patterson 提交于
This reverts commit 37423e4f. Jeremy is right that we shouldn't remove this. The fact is that many engines are depending on this middleware to be in the default stack. This ties our hands and forces us to keep the middleware in the stack so that engines will work. To be extremely clear, I think this is another smell of "the rack stack" that we have in place. When manipulating middleware, we should have meaningful names for places in the req / res lifecycle **not** have engines depend on a particular constant be in a particular place in the stack. This is a weakness of the API that we have to figure out a way to address before removing the constant. As far as timing attacks are concerned, we can reduce the granularity such that it isn't useful information for hackers, but is still useful for developers.
-
由 Eileen M. Uchitelle 提交于
Wrong usage of 'a' in docs fixed [ci skip]
-
由 Mehmet Emin İNAÇ 提交于
-
由 Sean Griffin 提交于
Add Singleton in NullMutationTracker class
-
由 Kasper Timm Hansen 提交于
Fixed deprecated string to specify the middleware [ci skip]
-
- 03 10月, 2015 9 次提交
-
-
由 acapilleri 提交于
to reduce allocation of same object
-
由 amitkumarsuroliya 提交于
-
由 Kasper Timm Hansen 提交于
Support passing array to `assert_enqueued_jobs` in `:only` option
-
由 Wojciech Wnętrzak 提交于
-
由 Kasper Timm Hansen 提交于
use class to specify the middleware [ci skip]
-
由 yuuji.yaginuma 提交于
using string for middleware class names is deprecated in 83b767ce
-
由 Aaron Patterson 提交于
The runtime header is a potential target for timing attacks since it returns the amount of time spent on the server (eliminating network speed). Total time is also not accurate for streaming responses. The middleware can be added back via: ```ruby config.middleware.ues ::Rack::Runtime ```
-
由 Rafael Mendonça França 提交于
Do not document private methods in AJ::TestHelper
-
由 Wojciech Wnętrzak 提交于
[CI skip]
-
- 02 10月, 2015 14 次提交
-
-
由 Sean Griffin 提交于
[ci skip] Fix explanation of `ActiveModel::Serialization`
-
由 Sean Griffin 提交于
Remove unused scopes
-
由 Sean Griffin 提交于
For reads, we never need to construct this object. The double `defined?` check is to avoid errors in tests
-
由 Andrew White 提交于
TimeWithZone#xmlschema should be able to display more than 6 digits
-
由 Sean Griffin 提交于
Fix AC::Parameters not being sanitized for query methods.
-
由 Sean Griffin 提交于
I misread this test in https://github.com/rails/rails/commit/1a693c79c32cba070256fdb7bd1990c3d07d554f
-
由 Sean Griffin 提交于
There were a few places where I missed a `create` vs `new` before_type_cast check, and the semantics of `reload` became wrong.
-
由 Sean Griffin 提交于
We can skip the allocation of a full `AttributeSet` by changing the semantics of how we structure things. Instead of comparing two separate `AttributeSet` objects, and `Attribute` is now a singly linked list of every change that has happened to it. Since the attribute objects are immutable, to apply the changes we simply need to copy the head of the list. It's worth noting that this causes one subtle change in the behavior of AR. When a record is saved successfully, the `before_type_cast` version of everything will be what was sent to the database. I honestly think these semantics make more sense, as we could have just as easily had the DB do `RETURNING *` and updated the record with those if we had things like timestamps implemented at the DB layer. This brings our performance closer to 4.2, but we're still not quite there.
-
由 Guo Xiang Tan 提交于
-
由 Jeremy Daer 提交于
Response#add_header for adding to multi-valued headers like Vary
-
由 Jeremy Daer 提交于
-
由 Andy Atkinson 提交于
-
由 yui-knk 提交于
This explanation was change by https://github.com/rails/rails/commit/7a27de2b. This change reversed the including module (`ActiveModel::Serializers::JSON`) and the included module (`ActiveModel::Serialization`) by mistake.
-
由 Jeremy Daer 提交于
Don't set a nil Set-Cookie header when there aren't any cookies
-