- 13 2月, 2016 21 次提交
-
-
由 Bogdan Gusiev 提交于
instead of loading the relation into memory
-
由 Kasper Timm Hansen 提交于
A callable cache key writes to the collection cache under a certain namespace. Which means if we don't have scoped cache key we can just rely on the `cache model_name do` in the templates to cache them. Less writes, more sharing. Add `assert_customer_cached` to better illustrate this in tests, and remove tests which then don't communicate as much.
-
由 Kasper Timm Hansen 提交于
It was difficult to see when the partials were rendered, and how many times we expected it to be rendered before. Because we weren't explaining it.
-
由 Rafael Mendonça França 提交于
-
由 Kasper Timm Hansen 提交于
`automatic_cache_eligible?´ is only called if there was no `:cache` key to fetch in the `@options` via `cache_collection?`. So the check will always be false.
-
由 Kasper Timm Hansen 提交于
When people pass `cache: -> item { item.upcase }` they scope the collection cache keys so the individual partial cache isn't reused. Test that behavior.
-
由 Aaron Patterson 提交于
-
由 Aaron Patterson 提交于
This will ensure that the digestor stays in parity with the LookupContext object.
-
由 Kasper Timm Hansen 提交于
Written when I didn't understand the internals as well. Action View generally just refers to `@template` when meaning a fixed template render. So follow that implicit convention.
-
由 Kasper Timm Hansen 提交于
We should only support a top level `cache_options`. We also don't have to default the options to a hash as Active Support's cache defaults that arg to nil.
-
由 Aaron Patterson 提交于
in the case of failure it is nice to see what the two digests are.
-
由 Aaron Patterson 提交于
we can use kwargs in this case to avoid values_at and except calls on the options hash
-
由 Kasper Timm Hansen 提交于
Fix routes to match verb and URL path with -g option also.
-
由 Kasper Timm Hansen 提交于
Yesterday, when improving how `parsed_body` extracted a parser I wrote 77bbf1e9. Then I thought that was too many changes in one commit and broke it up locally... or so I thought. When pushed the extra commits removed the changes! Wups! In shame, lob those changes together here: * 3b94c38a which meant to fix the CHANGELOG syntax error. * 5007df5e which meant to mention `parsed_body` in the docs. * 036a7a03 which meant to memoize the `parsed_body`.
-
由 Kasper Timm Hansen 提交于
Add more info about the APIs added and how they work. Use string keys when comparing the parsed response, like how JSON would be parsed.
-
由 Vipul A M 提交于
Fix 'config/production.rb' path in comment
-
由 Tom von Schwerdtner 提交于
s/config\/production/config\/environments\/production/ [ci skip]
-
由 Vipul A M 提交于
[ci skip] Fix enqueuing spelling to maintain consistency
-
由 Abhishek Jain 提交于
-
由 Rafael França 提交于
use rails instead of rake [ci skip]
-
由 Gaurav Sharma 提交于
since starting with Rails 5.x(beta) we prefer to use rails as the replacement of rake commands, may be change log will be the same
-
- 12 2月, 2016 19 次提交
-
-
由 Jon Moss 提交于
Update RELEASING_RAILS.md
-
由 Jon Moss 提交于
Koz is in alumni now, replaced him with rafaelfranca. [ci skip]
-
由 Kasper Timm Hansen 提交于
Fix argument passing to rake routes
-
由 Vipul A M 提交于
- Fixed related documentation and usage all around Fixes #23561
-
由 प्रथमेश Sonpatki 提交于
Fix numbers of steps to upgrade Rails [ci skip]
-
由 Prathamesh Sonpatki 提交于
-
由 Aaron Patterson 提交于
This metaprogrammed method doesn't seem to be a bottleneck, so lets just use a regular method so it's easier to understand. We can follow up with more interesting techniques for cache manipulation soon.
-
由 Jon Moss 提交于
Document the upgrade process
-
由 Leslie Viljoen 提交于
[ci skip]
-
由 Jon Moss 提交于
ActionCable README updates
-
由 Kasper Timm Hansen 提交于
It's common to use several assertions on the parsed response. The response bodies aren't meant to be mutated. People should make new test requests instead. Thus, it should be safe to memoize the parsing.
-
由 Kasper Timm Hansen 提交于
Little easier to understand when you know the method that's used.
-
由 Kasper Timm Hansen 提交于
Can't code for shit.
-
由 Kasper Timm Hansen 提交于
We're not guaranteed to have a `RequestEncoder` to assign on `get` requests because we aren't extracting the parser from the response content type. Until now.
-
由 Leslie Viljoen 提交于
The iterative process one has to follow is not currently documented, and people could be unfamiliar with the Rails versioning scheme, causing them to skip versions or upgrade to patch releases. [ci skip]
-
由 Kasper Timm Hansen 提交于
Wasn't removed in 57ac7774.
-
由 Aaron Patterson 提交于
-
由 Aaron Patterson 提交于
-
由 Aaron Patterson 提交于
then we can stop scattering nil checks (e.g. `try`) through the class.
-