| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
example domain
|
| |
|
|\ |
|
| |
| |
| |
| | |
the routes task
|
|/ |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
is too obscure, leaves the comparison to document the differences, and adds a comparison with the related idiom that uses the splat operator
|
|\ |
|
| |
| |
| |
| | |
for bundler
|
| | |
|
| | |
|
| | |
|
|/ |
|
|\ |
|
| |
| |
| |
| | |
for how it differs from Kernel#Array
|
| | |
|
| | |
|
|\ \ |
|
| | |
| | |
| | |
| | |
| | |
| | | |
I am working on removing all traces of superclass_delegating_accessor from rails code base.
https://rails.lighthouseapp.com/projects/8994/tickets/2914-superclass_delegating_accessor-needs-to-be-deprecated-nicely
|
|/ /
| |
| |
| | |
instead of former rails 3 format
|
| |
| |
| |
| | |
error messages with bundler
|
| | |
|
| | |
|
|/ |
|
|\ |
|
| |
| |
| |
| | |
to field_with_errors [#157 state:resolved]
|
| | |
|
|/ |
|
|
|
|
| |
mathematical sense [#5174 state:resolved]
|
| |
|
|
|
|
| |
plural
|
| |
|
|
|
|
| |
some paragraphs for clarity
|
| |
|
| |
|
|\ |
|
| | |
|
| |
| |
| |
| | |
docrails github wiki
|
| | |
|