| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
|
|
|
| |
This will help people figure out what credentials and tables are required to
run ActiveRecord specs.
|
|
|
|
| |
[ci skip]
|
| |
|
| |
|
|
|
|
|
|
| |
Since `Thor::HELP_MAPPINGS` contains `-D`, so `bin/rails -D` show
rails's help. But, in Rails 5.0.1, `bin/rails -D` show the description
of rake task. I think that it is better to have the same behavior.
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The exact inspect output of a BigDecimal is out of scope for what we're trying
to communicate about `dup` and `duplicable?` here.
Adding two examples distracts is disctracting, so keep the docs from before
since our minimal version is Ruby 2.2.2.
[ Koichi ITO, Jon Moss, Kasper Timm Hansen ]
This reverts commit 2163874dedaf83e67599c2930c2686caa165fbad, reversing
changes made to 46fdbc5290335ed38fa9fe2b6b0ef8abe4eccb1b.
|
|
|
|
| |
cf. https://github.com/ruby/bigdecimal/pull/42
|
|
|
|
|
| |
The Numeric extensions like 1.day, 1.month, etc. shouldn't know
how the internals of ActiveSupport::Duration works.
|
|\
| |
| | |
Fix inconsistent parsing of Durations with both months and years
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
durations from code
ActiveSupport::Duration.parse('P3Y') == 3.years # It should be true
Duration parsing made independent from any moment of time:
Fixed length in seconds is assigned to each duration part during parsing.
Changed duration of months and years in seconds to more accurate and logical:
1. The value of 365.2425 days in Gregorian year is more accurate
as it accounts for every 400th non-leap year.
2. Month's length is bound to year's duration, which makes
sensible comparisons like `12.months == 1.year` to be `true`
and nonsensical ones like `30.days == 1.month` to be `false`.
Calculations on times and dates with durations shouldn't be affected as
duration's numeric value isn't used in calculations, only parts are used.
Methods on `Numeric` like `2.days` now use these predefined durations
to avoid duplicating of duration constants through the codebase and
eliminate creation of intermediate durations.
|
|/
|
|
| |
https://github.com/rails/rails/commit/f02a35b86efea24f1e2ab684bc8081ced5eb3b1a [ci skip]
|
|\
| |
| | |
Update increment! documentation [ci skip]
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
The `increment!` and `decrement!` methods were recently reimplemented to
make them safe to call from multiple connections concurrently. This
changed their behaviour in a few ways.
Previously they used `update_attribute`, which calls the attribute
setter method, runs callbacks, and touches the record. Now they behave
more like `update_column`, writing the update to the database directly
and bypassing all of those steps.
|
| | |
|
|\ \
| | |
| | | |
Update asset fingerprinting information
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
- Replaced MD5 => SHA256 where necessary
- Updated sprockets manifest example
See: https://github.com/rails/sprockets/blob/dd9b3b53c06c602c49057bc4a426c1a446ed7a4a/lib/sprockets.rb#L26
|
|\ \ \
| | | |
| | | | |
Fix default locale code example [ci skip]
|
| | | | |
|
|/ / /
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Rails automatically finds bi-directional associations between models
with well-named associations. However, when using non-standard naming,
you have to use :inverse_of to explicitly tell Rails about the bi-
directional association.
With reference to #27516
[ci skip]
|
| | | |
|
| | | |
|
|\ \ \
| | | |
| | | | |
Update list of `duplicable?` objects in AS core_ext guide [ci skip]
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Complex and Rational objects can not be duplicated.
Duplicable objects in Ruby 2.4.0 include:
- most numbers
- symbols
- `nil`
- `true`
- `false`
|
| | | | |
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
jeremywadsack/doc_cache_importability""
This reverts commit 6961afefd2f163f30b9ae3aacb74b290287f9a80.
We were not able to keep backward compatibility in this case so it is
better to ask people to upgrade with cold cache.
|
| | | |
| | | |
| | | |
| | | | |
[ci skip]
|
| |/ /
|/| | |
|
| | | |
|
| | |
| | |
| | |
| | | |
Rewrite bits and pieces to mention the command infrastructure.
|
|\ \ \
| | | |
| | | | |
Add note on defaults block option
|
| | | |
| | | |
| | | | |
When I was looking for how to default the entire routes file to JSON I could only find the postfix option. It was mentioned on IRC that you could do this with a block as well and I had not found it in the documentation.
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
* How to disable scaffolds.scss in generators.md
* Improves workflow customization text in generators.md
|
| | | | |
|
|\ \ \ \
| |/ / /
|/| | | |
|
| | | |
| | | |
| | | |
| | | | |
Followup of https://github.com/rails/rails/pull/27086
|
| |/ /
|/| | |
|
| | |
| | |
| | |
| | |
| | | |
`assert_send` was deprecated in minitest 5.10.0.
Ref: https://github.com/seattlerb/minitest/commit/f95ef007ec64d956d88fedc37fd2ed7e106b777e
|
| | |
| | |
| | |
| | | |
Follow up to 79a5ea9eadb4d43b62afacedc0706cbe88c54496
|
| | | |
|
| | |
| | |
| | | |
[ci skip]
|
| | |
| | |
| | |
| | | |
auth [ci skip]
|
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
- Mentioned clearly that for PostgreSQL < 9.4, you need to pass the
default option with "uuid_generate_v4()"
- Also updated PostgreSQL Active Record guide with this change.
- https://github.com/rails/rails/pull/25395#r66877078
|
| | |
| | |
| | |
| | | |
[ci skip]
|
| | | |
|
|/ /
| |
| |
| |
| | |
section already speaks about sanitization as a safety measure. [ci skip] (#27086)
Fixes #27085
|
| |
| |
| |
| | |
Follow up to 7c848e6dd493ff236d33a0410a92f4c3e5cc3c7f
|
| |
| |
| | |
Changed "same way they do" to "same way they are".
|
|\ \
| | |
| | | |
Add missing `+` around a some literals.
|
| | |
| | |
| | |
| | |
| | |
| | | |
Mainly around `nil`
[ci skip]
|