| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This new coloration approach makes it easier to scan the rails console
for specific types of activity with more fine-grained visual cues.
Virtual terminal ANSI color escape codes are used when displaying SQL
statements in the rails console. The former implementation alternates
line prefix information (including the statement name and execution
latency) between CYAN and MAGENTA. This visually differentiates any SQL
statements in the log and is useful for quickly scanning for database
activity.
While a great idea and a solid foundation, alternating between just two
colors on an even/odd basis (much like striping an HTML table) can be
improved upon.
This patch replaces the even/odd striping with a more comprehensive
scheme that applies coloration based on the type of statement being
run. Every statement logged has its prefix (name and latency) colored
white (as the statement body was previously). The statement body is now
colored according to the nature of the statement:
- INSERT statements are GREEN (symbolic of creation or genesis)
- SELECT statements are BLUE (typically used for informational
displays, as SELECT statements do not normally have side-effects)
- DELETE statements are RED (commonly used to indicate the danger of
a destructive action)
- UPDATE statements are YELLOW (it's like a less extreme RED :P)
- TRANSACTION statements are CYAN (arbitrary)
- and any other statements are MAGENTA (again, arbitrary)
|
|\
| |
| | |
[ci skip] Make clear what `this method` is
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
In this sentence, there are three candidates of `this method`
* default_url_options
* url_for
* helper method(s)
so make it clear.
|
| | |
|
|/
|
|
|
|
|
|
|
|
|
| |
As of 56903585, the Rack::ContentLength middleware isn't included by
default anymore.
The only remaining middleware is Rack::Lock ; since it's only included
when using WEBrick, it's certainly not worth documenting it in the
guides.
[ci skip]
|
|\
| |
| |
| | |
[ci skip] correct for ActiveRecord::Associations::Preloader
|
| | |
|
|/ |
|
|\
| |
| |
| | |
Fix `undefined method uncached` for polymorphic belongs_to #20426
|
| |
| |
| |
| |
| |
| |
| | |
Unitialized polymorphic `belongs_to` associations raise an error while
attempting to reload, as they attempt to make an uncached reload, but
don't have a klass to fetch uncachedly. In this case, `loaded?` should
be `false` anyway.
|
|\ \
| | |
| | |
| | | |
thrown ActiveRecord::AssociationTypeMismatch when assigning a wrong value for a namespaced association
|
| | |
| | |
| | |
| | |
| | | |
for a namespaced association
fixes #20541
|
|\ \ \
| | | |
| | | | |
do not show "Failed tests" message when a failed test is not
|
| | | | |
|
|\ \ \ \
| | | | |
| | | | | |
Remove mistaken end from controller_path doc [ci skip]
|
| | |/ /
| |/| | |
|
|\ \ \ \
| | | | |
| | | | | |
Respect routing precedence for HEAD requests
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Fixes the issue described in #18764 - prevents Rack middleware from
swallowing up HEAD requests that should have been matched by a
higher-precedence `get` route, but still allows Rack middleware to
respond to HEAD requests.
|
|\ \ \ \ \
| | | | | |
| | | | | | |
Add nodoc to the Validations::Helpers [ci skip]
|
|/ / / / / |
|
|\ \ \ \ \
| |_|/ / /
|/| | | | |
Minor fixes [ci skip]
|
|/ / / / |
|
| | | |
| | | |
| | | |
| | | |
| | | | |
The heading "Active Model Length Validator" was shown on the
"ActiveModel::Validations" page without any text following it.
|
| | | |
| | | |
| | | |
| | | |
| | | | |
This is a small refactoring that simplifies the Active Record specific
lenght validator.
|
| | | | |
|
| |/ /
|/| |
| | |
| | | |
Associated objects that were marked for destruction are considered absent.
|
|\ \ \
| | | |
| | | | |
Move the validations HelperMethods to its own file
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Closes #11209
[Roque Pinel & Steven Yang]
|
|\ \ \ \
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
vngrs/strong_parameters_unpermitted_parameters_wrong_doc_fix
Fix the documentation about ActionController::UnpermittedParameters [ci skip]
|
|/ / / / |
|
|\ \ \ \
| | | | |
| | | | | |
remove unused variable in reporter test
|
| | | | | |
|
|\ \ \ \ \
| | | | | |
| | | | | | |
Fix the documentation about ActionController::ParameterMissing [ci skip]
|
| | |/ / /
| |/| | | |
|
|\ \ \ \ \
| |/ / / /
|/| | | | |
Remove duplicate private statement
|
| | | | | |
|
|\ \ \ \ \
| |/ / / /
|/| | | |
| | | | |
| | | | | |
Conflicts:
guides/source/configuring.md
|
| | | | |
| | | | |
| | | | | |
[ci skip]
|
| | | | |
| | | | |
| | | | |
| | | | | |
LookupContext is class name
|
| | | | | |
|
| | | | | |
|
| | | | |
| | | | |
| | | | |
| | | | | |
[ci skip]
|
| | | | |
| | | | |
| | | | |
| | | | | |
This is same type commit of https://github.com/rails/rails/pull/20463
|
| | | | | |
|
| | | | |
| | | | |
| | | | |
| | | | | |
Just saw these in passing while reading this file.
|
| | | | |
| | | | |
| | | | |
| | | | | |
Colons are not metacharacters.
|
|\ \ \ \ \
| |_|/ / /
|/| | | | |
fix test not failing when executed isolated
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
the test was created in 7659fb6
the fixtures were added in c092dbe
|
|/ / / /
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
After discussing, we've decided it makes more sense to include it. We're
already forwarding every conflicting method to `to_a`, and there's no
conflation of concerns. `Enumerable` has no mutating methods, and it
just allows us to simplify the code. No existing methods will have a
change in behavior. Un-overridden Enumerable methods will simply
delegate to `each`.
[Sean Griffin & bogdan]
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
This matches our behavior in other cases where useful enumerable methods
might have a different definition in `Relation`. Wanting to actually
enumerate over the records in this case is completely reasonable, and
wanting `.sum` is reasonable for the same reason it is on `Enumerable`
in the first place.
|