diff options
author | Sean Griffin <sean@seantheprogrammer.com> | 2017-07-17 11:14:11 -0400 |
---|---|---|
committer | Sean Griffin <sean@seantheprogrammer.com> | 2017-07-17 11:19:15 -0400 |
commit | 1519e976b224871c7f7dd476351930d5d0d7faf6 (patch) | |
tree | 994e25c414d75ce825b17cd3c6960b10a3a06c8d /actionview/test/fixtures/public/stylesheets/random.styles | |
parent | 828b05f5f9f8decf55170ea75bfdc6d37787993d (diff) | |
download | rails-1519e976b224871c7f7dd476351930d5d0d7faf6.tar.gz rails-1519e976b224871c7f7dd476351930d5d0d7faf6.tar.bz2 rails-1519e976b224871c7f7dd476351930d5d0d7faf6.zip |
Allow multiparameter assigned attributes to be used with `text_field`
Between 4.2 and 5.0 the behavior of how multiparameter attributes
interact with `_before_type_cast` changed. In 4.2 it returns the
post-type-cast value. After 5.0, it returns the hash that gets sent to
the type. This behavior is correct, but will cause an issue if you then
tried to render that value in an input like `text_field` or
`hidden_field`.
In this case, we want those fields to use the post-type-cast form,
instead of the `_before_type_cast` (the main reason it uses
`_before_type_cast` at all is to avoid losing data when casting a
non-numeric string to integer).
I've opted to modify `came_from_user?` rather than introduce a new
method for this as I want to avoid complicating that contract further,
and technically the multiparameter hash didn't come from assignment, it
was constructed internally by AR.
Close #27888.
Diffstat (limited to 'actionview/test/fixtures/public/stylesheets/random.styles')
0 files changed, 0 insertions, 0 deletions