aboutsummaryrefslogtreecommitdiffstats
path: root/guides
diff options
context:
space:
mode:
authorRyuta Kamizono <kamipo@gmail.com>2018-09-28 18:42:09 +0900
committerGitHub <noreply@github.com>2018-09-28 18:42:09 +0900
commit7d89337b1722587961b9bb81031661b99935d919 (patch)
tree3a1709bd113e6e2c457c55bfb0476555d78164a9 /guides
parent886d38e63eeba8c5973fa1968883f0d7456c45aa (diff)
parent4216e93e1a4ba7e1d5ace8de628e8bbdf4a661e6 (diff)
downloadrails-7d89337b1722587961b9bb81031661b99935d919.tar.gz
rails-7d89337b1722587961b9bb81031661b99935d919.tar.bz2
rails-7d89337b1722587961b9bb81031661b99935d919.zip
Merge pull request #33348 from ruralocity/update-validation-contexts-guide
Update guide for validation custom contexts [ci skip]
Diffstat (limited to 'guides')
-rw-r--r--guides/source/active_record_validations.md36
1 files changed, 27 insertions, 9 deletions
diff --git a/guides/source/active_record_validations.md b/guides/source/active_record_validations.md
index 3f13ef8d10..c98f24d786 100644
--- a/guides/source/active_record_validations.md
+++ b/guides/source/active_record_validations.md
@@ -844,9 +844,9 @@ class Person < ApplicationRecord
end
```
-You can also use `on:` to define custom context.
-Custom contexts need to be triggered explicitly
-by passing name of the context to `valid?`, `invalid?` or `save`.
+You can also use `on:` to define custom contexts. Custom contexts need to be
+triggered explicitly by passing the name of the context to `valid?`,
+`invalid?`, or `save`.
```ruby
class Person < ApplicationRecord
@@ -854,14 +854,32 @@ class Person < ApplicationRecord
validates :age, numericality: true, on: :account_setup
end
-person = Person.new
+person = Person.new(age: 'thirty-three')
+person.valid? # => true
+person.valid?(:account_setup) # => false
+person.errors.messages
+ # => {:email=>["has already been taken"], :age=>["is not a number"]}
```
-`person.valid?(:account_setup)` executes both the validations
-without saving the model. And `person.save(context: :account_setup)`
-validates `person` in `account_setup` context before saving.
-On explicit triggers, model is validated by
-validations of only that context and validations without context.
+`person.valid?(:account_setup)` executes both the validations without saving
+the model. `person.save(context: :account_setup)` validates `person` in the
+`account_setup` context before saving.
+
+When triggered by an explicit context, validations are run for that context,
+as well as any validations _without_ a context.
+
+```ruby
+class Person < ApplicationRecord
+ validates :email, uniqueness: true, on: :account_setup
+ validates :age, numericality: true, on: :account_setup
+ validates :name, presence: true
+end
+
+person = Person.new
+person.valid?(:account_setup) # => false
+person.errors.messages
+ # => {:email=>["has already been taken"], :age=>["is not a number"], :name=>["can't be blank"]}
+```
Strict Validations
------------------