- 11 8月, 2015 21 次提交
-
-
由 Aaron Patterson 提交于
we only need to check for `path` once.
-
由 Rafael Mendonça França 提交于
[ci skip] Add link to testing guide
-
由 Rafael Mendonça França 提交于
Make assert_enqueued_with and assert_performed_with returns the matched job
-
由 Jean Boussier 提交于
-
由 Aaron Patterson 提交于
Now we can see where `defaults` options originate
-
由 Aaron Patterson 提交于
-
由 Aaron Patterson 提交于
since `controller` and `controller_scope` were the same, just combine them
-
由 Aaron Patterson 提交于
-
由 Aaron Patterson 提交于
This method isn't used internally, isn't tested, isn't documented. We should delete it.
-
由 Aaron Patterson 提交于
add a predicate method so that we can avoid is_a? calls on the resource object.
-
由 Aaron Patterson 提交于
calling `scope` isn't cheap, so try to call cheaper methods that do the same thing for those particular parameters (in this case `path_scope`)
-
由 Aaron Patterson 提交于
`resource_scope` should just put resource scopes on the stack, and doesn't need to know what a `scope_level` is.
-
由 Aaron Patterson 提交于
We just want to augment the scope level, not the frame itself, so just copy the frame to the new scope object.
-
由 Kasper Timm Hansen 提交于
-
由 Rafael Mendonça França 提交于
Update info on browser connection limits [ci skip]
-
由 Derek Prior 提交于
Browsers have not been limited to two connections per host for quite some time now. With more connections allowed, the trade-off involved in asset host distribution isn't so clear and it becomes more important that developers measure actual performance before and after.
-
由 Aaron Patterson 提交于
this gives us an easier way to iterate the stack
-
由 Aaron Patterson 提交于
The same information is stored in the `@scope` linked list, so just get it from there.
-
由 Aaron Patterson 提交于
this lets us remove the setter and make the Resource object Read-Only
-
由 Aaron Patterson 提交于
We don't need to ask `scope` for the resource because we already have it right here.
-
由 Brooks Reese 提交于
-
- 10 8月, 2015 15 次提交
-
-
由 Abdelkader Boudih 提交于
[ci skip] Modify introduction to be consistent with other guides
-
由 Brooks Reese 提交于
-
由 Yves Senn 提交于
Closes #21121
-
由 Kasper Timm Hansen 提交于
Reload I18n.load_path in development
-
由 Rafael Mendonça França 提交于
-
由 Rafael Mendonça França 提交于
make generated scaffold functional tests work inside API engines
-
由 Rafael Mendonça França 提交于
This method raises conditionally not always so we should not documment as it always raise.
-
由 Rafael Mendonça França 提交于
-
由 Rafael Mendonça França 提交于
We should return when the contoller key is not present or if the controller doesn't exist and we didn't raised an error.
-
由 Rafael Mendonça França 提交于
Related with dc1b937d
-
由 Rafael Mendonça França 提交于
-
由 Aaron Patterson 提交于
eliminates calling `scope` in one method, pushes the other calls up one frame. This goes a little way towards eliminating the internal calls to `scope`.
-
由 Kir Shatrov 提交于
-
由 Claudio B. 提交于
[ci skip] Note that each action maps to a specific CRUD operation
-
由 Brooks Reese 提交于
-
- 09 8月, 2015 4 次提交
-
-
由 yuuji.yaginuma 提交于
* set engine's route in setup * use fixture with engine namespace
-
由 Aaron Patterson 提交于
we don't really need this hash.
-
由 Aaron Patterson 提交于
we need to get a grip on what `scope` actually does. This commit removes some of the internal calls to `scope`. Eventually we should add public facing methods that provide the API that `scope` is trying to accomplish.
-
由 Aaron Patterson 提交于
`prepare_params!` would raise an exception if `params` wasn't initialized, so it must always be available. Remove the existence conditional from the `controller` method.
-