| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
* Update url in Development Dependencies Install
|
|
|
|
|
|
| |
Lots of grammar cleanup, and also changing to use macOS.
[ci skip]
|
|
|
|
|
|
|
|
| |
This is a requirement when working on the JS portions of ASt. Using
npm instead of Yarn is a bad idea here since the lockfile is in Yarn's
format.
[ci skip]
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The initial commit (efaa6e4f79d457c2cdd08cbc56d63bc972a6993c) that changed this
behavior was intended to be a minor change, but ended up becoming a
large-ish breaking change within Active Record.
This is because instead of only JSON encoding `Hash`es or `Array`s in `#serialize`,
we now encode all values passed in. This is an issue if you're passing in a `String`,
that has already been transformed from a `Hash` to a `String`, since your data
is now being double encoded.
Unfortunately, the change was included in one of the v5.0.0 beta
releases, and it is too late to revert without huge ripple effects.
Thus, all we can do is update the documentation (via this commit), and
add some test coverage (coming soon in a PR) for the new behavior.
Please note that in the documentation I talk about deserialization, not
about serialization, where the actual change occurred. This is because
you won't notice any changes in serialized data until you try and
deserialize it. Also to make the change itself (confusing until you
read through everything multiple times) easier to understand.
Related #27788, #25594, #26101, #24234, #28292, #28285, #28285, and
probably others.
[ci skip]
|
|
|
|
|
|
| |
about passing string to `:if` and `:unless`.
This is a follow up to https://github.com/rails/rails/pull/28058 [ci
skip]
|
|
|
|
|
|
| |
Changed sentence to be more clear
[ci skip]
|
|
|
|
|
|
| |
`it` and `has` are for singular, not plural
[ci skip]
|
|
|
|
|
|
| |
Periods should be outside of the <a> tags
[ci skip]
|
|\
| |
| | |
Update guides/source/plugins.md [ci skip]
|
| | |
|
|/ |
|
| |
|
| |
|
| |
|
| |
|
|\
| |
| | |
Improve callback examples in Active Job guide
|
| | |
|
| |
| |
| |
| | |
The advice for symbol/block form is taken from the Active Record guides.
|
|\ \
| | |
| | | |
Fix generator example code [ci skip]
|
| | | |
|
|/ / |
|
| | |
|
|\ \
| | |
| | | |
add reload_association to documentation
|
| | | |
|
| | | |
|
|/ /
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
In some examples and guides we are recommending to use code like:
```ruby
verified_user = User.find_by(id: cookies.signed[:user_id])
```
My suggestion is to use instead:
```ruby
verified_user = User.find_by(id: cookies.encrypted[:user_id])
```
which invites users to prefer the "newer" encrypted cookies over the
"legacy" signed cookies.
|
| |
| |
| |
| |
| |
| |
| | |
Should _probably_ be done across the board with all of our
documentation, but going to leave that for another time :)
[ci skip]
|
| |
| |
| |
| | |
[ci skip]
|
|/
|
|
| |
work as intended. [ci skip]
|
| |
|
| |
|
|
|
|
|
| |
It seems that it accepts only HTTPS connections.
Ref: https://github.com/postgres/postgres/commit/7f77cbd996855a06fb742ea11adbe55c42b48fe2
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
commit 4a3d295f3011e771cddead80de7497ca15d15c13
Author: Yauheni Dakuka <yauheni.dakuka@gmail.com>
Date: Fri Jul 28 14:31:35 2017 +0300
Update routing.md
commit 620a4ce47288e3ef6504290c78f931214968e7e3
Author: Yauheni Dakuka <yauheni.dakuka@gmail.com>
Date: Fri Jul 28 14:19:29 2017 +0300
[ci skip] update routing guide
|
| |
|
|
|
|
| |
callbacks
|
|\
| |
| | |
Updates Rails upgrade guide on `ActionView::Helpers::RecordTagHelper`
|
| |
| |
| |
| | |
`ActionView::Helpers::RecordTagHelper`
|
|\ \
| | |
| | | |
Fixing "Adding Member Routes" documentation
|
| | |
| | |
| | | |
Previously said the helpers were preview_photo_url and preview_photo_path, i.e. action_resource, when in fact they are resource_action. i.e. photo_preview_path. Fixed.
|
|\ \ \
| | | |
| | | | |
Add documentation for class_attribute default option
|
| | | | |
|
|\ \ \ \
| | | | |
| | | | | |
Set `represent_boolean_as_integer` via `configuration`
|
| | | | | |
|
|/ / / / |
|
|\ \ \ \
| | | | |
| | | | | |
Fix boolean column migration script
|
| | |_|/
| |/| | |
|
| | | |
| | | |
| | | |
| | | | |
basis that if it was simple, the user wouldn't be reading the docs
|
|/ / / |
|
|\ \ \
| | | |
| | | | |
Change sqlite3 boolean serialization to use 1 and 0
|
| |/ /
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Abstract boolean serialization has been using 't' and 'f', with MySQL
overriding that to use 1 and 0.
This has the advantage that SQLite natively recognizes 1 and 0 as true
and false, but does not natively recognize 't' and 'f'.
This change in serialization requires a migration of stored boolean data
for SQLite databases, so it's implemented behind a configuration flag
whose default false value is deprecated. The flag itself can be
deprecated in a future version of Rails. While loaded models will give
the correct result for boolean columns without migrating old data,
where() clauses will interact incorrectly with old data.
While working in this area, also change the abstract adapter to use
`"TRUE"` and `"FALSE"` as quoted values and `true` and `false` for
unquoted. These are supported by PostreSQL, and MySQL remains
overriden.
|