- 08 7月, 2017 1 次提交
-
-
由 Jahfer Husain 提交于
ActiveModel::Errors#merge! allows ActiveModel::Errors to append errors from a separate ActiveModel::Errors instance onto their own. Example: person = Person.new person.errors.add(:name, :blank) errors = ActiveModel::Errors.new(Person.new) errors.add(:name, :invalid) person.errors.merge!(errors) puts person.errors.messages # => { name: ["can't be blank", "is invalid"] }
-
- 28 6月, 2017 1 次提交
-
-
由 Ryuta Kamizono 提交于
[ci skip]
-
- 27 5月, 2017 1 次提交
-
-
由 Bradley Priest 提交于
a user input for a decimal column were ignored by numerically validations
-
- 30 4月, 2017 1 次提交
-
-
由 Ryuta Kamizono 提交于
* Remove trailing spaces. * Add backticks around method and command. * Fix indentation.
-
- 29 3月, 2017 1 次提交
-
-
由 Jon Moss 提交于
This CHANGELOG.md is a continuation of the 5-1-stable one, there shouldn't be any duplicate entries. [ci skip]
-
- 28 3月, 2017 1 次提交
-
-
由 bogdanvlviv 提交于
Before: person.errors.keys # => [] person.errors.values # => [] person.errors[:name] # => [] person.errors.keys # => [:name] person.errors.values # => [[]] After: person.errors.keys # => [] person.errors.values # => [] person.errors[:name] # => [] person.errors.keys # => [] person.errors.values # => [] Related to #23468
-
- 22 3月, 2017 1 次提交
-
-
由 Matthew Draper 提交于
-
- 24 2月, 2017 1 次提交
-
-
由 Rafael Mendonça França 提交于
-
- 18 2月, 2017 1 次提交
-
-
由 namusyaka 提交于
-
- 07 2月, 2017 2 次提交
-
-
由 Rafael Mendonça França 提交于
-
由 yuuji.yaginuma 提交于
`ActiveModel::TestCase` is used only for the test of Active Model. Also, it is a private API and can not be used in applications. Therefore, it is not necessary to include it in lib.
-
- 22 11月, 2016 1 次提交
-
-
由 Kenichi Kamiya 提交于
`#[]` has already applied indifferent access, but some methods does not. `#include?`, `#has_key?`, `#key?`, `#delete` and `#full_messages_for`.
-
- 15 10月, 2016 1 次提交
-
-
由 Iain Beeston 提交于
ie. DecimalWithoutScale, Text and UnsignedInteger
-
- 11 10月, 2016 2 次提交
-
-
由 Rafael Mendonça França 提交于
-
由 Rafael Mendonça França 提交于
`#get`, `#set`, `[]=`, `add_on_empty` and `add_on_blank`.
-
- 10 5月, 2016 1 次提交
-
-
由 Rafael Mendonça França 提交于
-
- 07 5月, 2016 1 次提交
-
-
由 Rafael Mendonça França 提交于
-
- 06 5月, 2016 1 次提交
-
-
由 Prathamesh Sonpatki 提交于
- Improve CHANGELOG entry for #18439. - The documentation is updated as per changes in PR #18439 to the `accept` option. - The explanation about the virtual attribute is moved at the end so that the arity of `accept` option is explained first. - Added a note that `message` can also be passed to `validates_acceptance_of`.
-
- 28 4月, 2016 1 次提交
-
-
由 eileencodes 提交于
-
- 05 4月, 2016 1 次提交
-
-
由 Prathamesh Sonpatki 提交于
- Pass object to I18n helper so that when calling message proc, it will pass that object as argument to the proc and we can generate custom error messages based on current record being validated. - Based on https://github.com/rails/rails/issues/856. [Łukasz Bandzarewicz, Prathamesh Sonpatki]
-
- 25 2月, 2016 1 次提交
-
-
由 eileencodes 提交于
Adds changelog headers for beta3 release
-
- 02 2月, 2016 1 次提交
-
-
由 Sean Griffin 提交于
-
- 06 1月, 2016 1 次提交
-
-
由 Rafael Mendonça França 提交于
While the type definition is in Active Model the change of behavior will be only user facing in Active Record so better to put the entry in its changelog. [ci skip]
-
- 05 1月, 2016 1 次提交
-
-
由 Andrey Novikov 提交于
-
- 21 12月, 2015 2 次提交
-
-
由 Genadi Samokovarov 提交于
During the `5.0.0.beta1` release, the CHANGELOGs got an entry like the following: ``` * No changes. ``` It is kinda confusing as there are indeed changes after it. Not a biggie, just a small pass over the CHANGELOGs. [ci skip]
-
由 Jon Atack 提交于
-
- 19 12月, 2015 1 次提交
-
-
由 eileencodes 提交于
-
- 02 10月, 2015 1 次提交
-
-
由 Roque Pinel 提交于
Move from `AS::Callbacks::CallbackChain.halt_and_display_warning_on_return_false` to `AS::Callbacks.halt_and_display_warning_on_return_false` base on [this discussion](https://github.com/rails/rails/pull/21218#discussion_r39354580) Fix the documentation broken by 0a120a81
-
- 09 9月, 2015 1 次提交
-
-
由 Semyon Pupkov 提交于
-
- 08 9月, 2015 2 次提交
-
-
由 Dmitry Polushkin 提交于
Example: ```ruby class Person include ActiveModel::Validations attr_reader :name, :title validates_presence_of :name, on: :create validates_presence_of :title, on: :update end person = Person.new person.valid?([:create, :update]) # => true person.errors.messages # => {:name=>["can't be blank"], :title=>["can't be blank"]} ```
-
由 Rafael Mendonça França 提交于
This reverts commit 51dd2588, reversing changes made to ecb4e4b2. This broke Active Record tests
-
- 01 9月, 2015 1 次提交
-
-
由 Akshat Sharma 提交于
Case :- 1. In case of email confirmation one needs case insensitive comparison 2. In case of password confirmation one needs case sensitive comparison [ci skip] Update Guides for case_sensitive option in confirmation validation
-
- 07 8月, 2015 1 次提交
-
-
由 Zachary Scott 提交于
This includes the following classes: - ActiveModel::Serializers::Xml - ActiveRecord::Serialization::XmlSerializer
-
- 30 7月, 2015 1 次提交
-
-
由 Dmitry Polushkin 提交于
Example: ```ruby class Person include ActiveModel::Validations attr_reader :name, :title validates_presence_of :name, on: :create validates_presence_of :title, on: :update end person = Person.new person.valid?([:create, :update]) # => true person.errors.messages # => {:name=>["can't be blank"], :title=>["can't be blank"]} ```
-
- 23 5月, 2015 1 次提交
-
-
由 karanarora 提交于
spelling fix [ci skip] example to be consistent [ci skip] grammatical fix typo fixes [ci skip]
-
- 29 4月, 2015 1 次提交
-
-
由 Jay Elaraj 提交于
`ActiveModel::Serialization#serializable_hash`
-
- 22 4月, 2015 2 次提交
-
-
由 Yves Senn 提交于
-
由 Fernando Tapia Rico 提交于
`ActiveModel::Dirty#[attr_name]_previous_change` to improve access to recorded changes after the model has been saved. It makes the dirty-attributes query methods consistent before and after saving.
-
- 05 4月, 2015 1 次提交
-
-
由 Robin Dupret 提交于
-
- 30 3月, 2015 1 次提交
-
-
由 Sean Griffin 提交于
As demonstrated by #19570, this option is severely limited, and satisfies an extremely specific use case. Realistically, there's not much reason for this option to exist. Its functionality can be trivially replicated with a normal Ruby method. Let's deprecate this option, in favor of the simpler solution.
-