kotovalexarian-likes-github/rails--rails
1
0
Fork 0
mirror of https://github.com/rails/rails.git synced 2022-11-09 12:12:34 -05:00
Code Releases Activity
rails--rails/activemodel/CHANGELOG.md

46 lines
1.5 KiB
Markdown
Raw Normal View History

Allows you to check if an attribute has changed to a particular value model.name_changed?(from: "Pete", to: "Ringo")
2013-12-01 23:50:43 -05:00
* `attribute_changed?` now accepts parameters which check the old and new value of the attribute
`model.name_changed?(from: "Pete", to: "Ringo")`
*Tejas Dinkar*
Use bcrypt's public cost attr, not internal constant See: - https://github.com/codahale/bcrypt-ruby/pull/63 - https://github.com/codahale/bcrypt-ruby/pull/64 - https://github.com/codahale/bcrypt-ruby/pull/65
2013-09-23 14:46:41 -04:00
* Fix `has_secure_password` to honor bcrypt-ruby's cost attribute.
*T.J. Schuck*
Merge pull request #8791 from griffinmyers/master Updated DirtyModel's @changed_attributes hash to be symbol/string agnostic Conflicts: activemodel/CHANGELOG.md
2013-10-03 10:37:10 -04:00
* Updated the `ActiveModel::Dirty#changed_attributes` method to be indifferent between using
DirtyModel uses a hash to keep track of any changes made to attributes of an instance. When using the attribute_will_change! method, you must supply a string and not a symbol or the *_changed? method will break (because it is looking for the attribute name as a string in the keys of the underlying hash). To remedy this, I simply made the underlying hash a HashWithIndifferentAccess so it won't matter if you supply the attribute name as a symbol or string to attribute_will_change!.
2013-01-07 00:04:35 -05:00
symbols and strings as keys.
*William Myers*
first pass through CHANGELOGS to extract 4_1_release_notes. [ci skip] Extract **notable changes**, **deprecations** and **removals** from each CHANGELOG. I tried to reference the commits and pull requests for new features and deprecations. In the process I also made some minor changes to the CHANGELOGS. The 4_1_release_notes guide is declared WIP.
2013-11-28 11:21:18 -05:00
* Added new API methods `reset_changes` and `changes_applied` to `ActiveModel::Dirty`
Merge pull request #10816 from bogdan/less-dirty-dirty Make AM::Dirty less dirty to plugin into AR or other library
2013-09-23 09:59:05 -04:00
that control changes state. Previsously you needed to update internal
instance variables, but now API methods are available.
*Bogdan Gusiev*
Use a better method name to check the requirement of password confirmation Also improve changelog entries related to secure password to proper highlight.
2014-01-07 04:59:24 -05:00
* Fix `has_secure_password` not to trigger `password_confirmation` validations
if no `password_confirmation` is set.
Fix secure_password password_confirmation validations
2013-06-25 20:46:21 -04:00
*Vladimir Kiselev*
Merge pull request #10774 from chuckbergeron/validates-inclusion-of-accuracy-for-non-numeric-ranges Greater accuracy for validates_inclusion_of on non-numeric ranges Closes #10774, fixes #10593
2013-06-25 20:46:50 -04:00
* `inclusion` / `exclusion` validations with ranges will only use the faster
`Range#cover` for numerical ranges, and the more accurate `Range#include?`
for non-numerical ones.
Fixes range validations like `:a..:f` that used to pass with values like `:be`.
first pass through CHANGELOGS to extract 4_1_release_notes. [ci skip] Extract **notable changes**, **deprecations** and **removals** from each CHANGELOG. I tried to reference the commits and pull requests for new features and deprecations. In the process I also made some minor changes to the CHANGELOGS. The 4_1_release_notes guide is declared WIP.
2013-11-28 11:21:18 -05:00
Fixes #10593.
Use Range#cover? for Numeric ranges (tests via endpoints) and use Range#include? for non-numeric ranges added changelog message
2013-05-28 02:07:05 -04:00
*Charles Bergeron*
Use a better method name to check the requirement of password confirmation Also improve changelog entries related to secure password to proper highlight.
2014-01-07 04:59:24 -05:00
* Fix regression in `has_secure_password`. When a password is set, but a
Fix regression in has_secure_password. If the confirmation was blank, but the password wasn't, it would still save.
2013-05-20 15:13:21 -04:00
confirmation is an empty string, it would incorrectly save.
*Steve Klabnik* and *Phillip Calvin*
deprecate Validator#setup (to get rid of a respond_to call). validators do their setup in their constructor now.
2013-05-12 23:59:28 -04:00
* Deprecate `Validator#setup`. This should be done manually now in the validator's constructor.
*Nick Sutterer*
Update CHANGELOGS
2013-02-26 11:45:20 -05:00
rails/master is now 4.1.0.beta
2013-04-29 12:06:45 -04:00
Please check [4-0-stable](https://github.com/rails/rails/blob/4-0-stable/activemodel/CHANGELOG.md) for previous changes.
Copy permalink