| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Rubinius returns a boolean after such assingment
response = (_, headers, body = @app.call(env))
see https://github.com/rubinius/rubinius/issues/2117
get rid of a local variable
|
|\ \ \ \ \ \
| |/ / / / /
|/| / / / /
| |/ / / / |
Fix error raised when assigning NaN to an integer column
|
|/ / / /
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Also covers any non-castable case by returning nil, which
is in-line with the intention of the former implementation,
but covers the odd cases which respond to to_i but raise
an error when it's called, such as NaN, Infinity and -Infinity.
Fixes #8757
|
| | | | |
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
* dependencies/autoload
* concern
* deprecation
|
|\ \ \ \
| | | | |
| | | | | |
refactor the naming within plugin new generator
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Having a method called `full?`, which checks on :full and :mountable
is very confusing. I renamed `full?` to `engine?` and created a `full?`
method that only checks the `:full` option
|
|\ \ \ \ \
| | | | | |
| | | | | | |
Fix img width in guides
|
| | | | | | |
|
|\ \ \ \ \ \
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
Require 'active_support/core_ext/module/aliasing' in the infinite_comparable module
When requiring 'active_support/core_ext', the following error is raised:
undefined method `alias_method_chain' for Date:Class (NoMethodError)
Adding the missing require to this module fixes the problem.
|
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
module
|
| | | | | | | |
|
| | | | | | | |
|
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
* core_ext/object/blank
* concern
* core_ext/class/attribute
* deprecation
|
|/ / / / / /
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Avoid swallowing all exceptions that might happen when requiring
debugger, just catch a LoadError if it cannot be loaded.
Check for more background:
https://github.com/rails/rails/commit/28fd867c9bc790636d37a28f288791cd0089a6fd#commitcomment-2386952
|
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
It is used by the table formatter only, and it's already inside a routes
directory that namespaces it properly, so calling it just "table" seems
simpler.
|
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
It feels more consistent to have this class called "HtmlTableFormatter",
and to have it here with the routes inspector and console formatter,
since it's used for both routing error exceptions and the rails info
page.
|
|\ \ \ \ \ \
| | | | | | |
| | | | | | | |
Delegate to :class rather than 'self.class'
|
| | | | | | | |
|
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
By checking for object.persisted? first, we avoid the hash lookups for
new objects.
|
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
When dealing with nested forms, Rails automatically generates a hidden
field with the id value of the current object being generated by
fields_for. This logic was inside the method that's available from the
template object, but we just need it when really dealing with nested
attributes, so moving the code to here makes more sense.
|
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
Just use it internally from fields_for until we come up with a better solution.
|
| | | | | | | |
|
| | | | | | | |
|
|\ \ \ \ \ \ \
| | | | | | | |
| | | | | | | | |
Refactor Route#ast to use or-equals and block, instead of return with a check
|
| | | | | | | | |
|
| | | | | | | | |
|
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | | |
should read more about the consequences than just toggling a boolean to make best use of it
|
|/ / / / / / /
| | | | | | |
| | | | | | |
| | | | | | | |
config/initializers to take effect
|
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
* a controller that destroying Weblogs might be WeblogsController
* a controller that indexing Posts might be PostsController
* Post.all returns a Relation
* modernize Model.inspect results
|
| | | | | | | |
|
| | | | | | | |
|
| | | | | | | |
|
|/ / / / / /
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
* it does not generate fixtures
* it generates .text.erb templates
|
|\ \ \ \ \ \
| |_|_|/ / /
|/| | | | | |
Prefer do-end for multiline block [ci skip]
|
|/ / / / / |
|
|\ \ \ \ \
| | | | | |
| | | | | | |
Fix guides' warning bottom padding
|
|/ / / / / |
|
| | | | | |
|
|\ \ \ \ \
| | | | | |
| | | | | | |
New code examples on "Working with JavaScript in Rails" guide.
|
| | | | | | |
|
|/ / / / / |
|
| | | | |
| | | | |
| | | | |
| | | | | |
This is very rarely changed and does not deserve to be in application.rb
|
|\ \ \ \ \
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Remove suggestion that Procs can be used as session secrets.
[ci skip]
|
| | | | | | |
|
| | | | | | |
|
| | | | | | |
|
| | | | | | |
|
| |/ / / /
|/| | | | |
|
|\ \ \ \ \
| | | | | |
| | | | | | |
deprecate `assert_blank` and `assert_present`.
|