| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
| |
We already know how to handle `path`, so lets just handle it on our own.
|
|
|
|
|
|
|
| |
All callers of `action_path` interpolate the return value in to a
string, so there is no need for the method to to_s it. to_sym on a
symbol will return the same symbol, though I think `action_path` may
always be called with a symbol so this might not be necessary.
|
|
|
|
| |
we only need to check for `path` once.
|
|\
| |
| | |
[ci skip] Add link to testing guide
|
| | |
|
|\ \
| | |
| | | |
Make assert_enqueued_with and assert_performed_with returns the matched job
|
| | | |
|
| | |
| | |
| | |
| | | |
Now we can see where `defaults` options originate
|
| | | |
|
| | |
| | |
| | |
| | |
| | | |
since `controller` and `controller_scope` were the same, just combine
them
|
|/ / |
|
| |
| |
| |
| |
| | |
This method isn't used internally, isn't tested, isn't documented. We
should delete it.
|
| |
| |
| |
| |
| | |
add a predicate method so that we can avoid is_a? calls on the resource
object.
|
| |
| |
| |
| |
| | |
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`)
|
| |
| |
| |
| |
| | |
`resource_scope` should just put resource scopes on the stack, and
doesn't need to know what a `scope_level` is.
|
| |
| |
| |
| |
| | |
We just want to augment the scope level, not the frame itself, so just
copy the frame to the new scope object.
|
| | |
|
|\ \
| | |
| | | |
Update info on browser connection limits [ci skip]
|
| |/
| |
| |
| |
| |
| |
| | |
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.
|
| |
| |
| |
| | |
this gives us an easier way to iterate the stack
|
| |
| |
| |
| |
| | |
The same information is stored in the `@scope` linked list, so just get
it from there.
|
| |
| |
| |
| | |
this lets us remove the setter and make the Resource object Read-Only
|
|/
|
|
|
| |
We don't need to ask `scope` for the resource because we already have it
right here.
|
|\
| |
| | |
[ci skip] Modify introduction to be consistent with other guides
|
|/
|
|
| |
guides
|
|
|
|
| |
Closes #21121
|
|\
| |
| | |
Reload I18n.load_path in development
|
| | |
|
| | |
|
|\ \
| | |
| | | |
make generated scaffold functional tests work inside API engines
|
| | |
| | |
| | |
| | |
| | | |
* set engine's route in setup
* use fixture with engine namespace
|
| | |
| | |
| | |
| | |
| | | |
This method raises conditionally not always so we should not documment
as it always raise.
|
| | | |
|
| | |
| | |
| | |
| | |
| | | |
We should return when the contoller key is not present or if the
controller doesn't exist and we didn't raised an error.
|
| | |
| | |
| | |
| | | |
Related with dc1b937db780155089fce522f03d340e62f5df36
|
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | | |
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`.
|
|\ \ \
| |/ /
|/| | |
[ci skip] Note that each action maps to a specific CRUD operation
|
| | | |
|
| | |
| | |
| | |
| | | |
we don't really need this hash.
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
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.
|
| | |
| | |
| | |
| | |
| | |
| | | |
`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.
|
| | |
| | |
| | |
| | |
| | | |
The method we called already has the conditional we need. Just add an
else block so that we don't need two tests.
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
`Dispatcher` doesn't need to hold on to the defaults hash. It only used
the hash to determine whether or not it should raise an exception if
there is a name error. We can pass that in further up the stack and
alleviate Dispatcher from knowing about that hash.
|
| | |
| | |
| | |
| | |
| | |
| | | |
We know in advance whether the object is a dispatcher or not, so we can
configure the Constraints object with a strategy that will call the
right method.
|
| | | |
|
| | |
| | |
| | |
| | | |
it isn't used.
|
|\ \ \
| | | |
| | | | |
Reference actual classes
|
| | | | |
|