dependent-auto-rails 0.2.0 → 0.2.2
Sign up to get free protection for your applications and to get access to all the features.
- checksums.yaml +4 -4
- data/README.md +5 -3
- data/lib/dependent-auto-rails/version.rb +1 -1
- metadata +2 -2
checksums.yaml
CHANGED
@@ -1,7 +1,7 @@
|
|
1
1
|
---
|
2
2
|
SHA256:
|
3
|
-
metadata.gz:
|
4
|
-
data.tar.gz:
|
3
|
+
metadata.gz: 6efa1cf923a9e588a447a663f138eec13d170870d89e1094d3a9cb87ace1838b
|
4
|
+
data.tar.gz: ce625776f26ef1c60886fa42bd7f4ca6e86da50e61fd8349562009b771bcf0a8
|
5
5
|
SHA512:
|
6
|
-
metadata.gz:
|
7
|
-
data.tar.gz:
|
6
|
+
metadata.gz: 7c1ee47b3eb695cc559cccdd922de6e70ebf87b12ac3810137cedcde4743af1681457445804f8bac366204b39735a381ed4d68ac82d9b0db5681d079a837ef07
|
7
|
+
data.tar.gz: e3014ef0129f2a82c1479e9fc4fe94b9b3c7684d9f93fd37543e0f04351f3fc4df3c2dba9dd8584150fd9305ad7ced379d2a6a59043e541833205c5c5c34d077
|
data/README.md
CHANGED
@@ -3,11 +3,11 @@
|
|
3
3
|
|
4
4
|
# dependent-auto-rails
|
5
5
|
|
6
|
-
This gem provides a new `dependent` option for ActiveRecord associations, `:auto`. Using this option will automatically select between `:destroy` and `:delete` / `:delete_all` during runtime based on whether or not the associated model has any callbacks defined which would usually be executed as part of the destroy lifecycle.
|
6
|
+
This gem provides a new `dependent` option for ActiveRecord associations, `:auto`. Using this option will automatically select between `:destroy` and `:delete` / `:delete_all` during runtime based on whether or not the associated model has any callbacks defined which would usually be executed as part of the destroy lifecycle.
|
7
7
|
|
8
|
-
|
8
|
+
This is useful since `dependent: :destroy` always initialises the associated records in order to execute their callbacks regardless of whether or not there are any defined, but is often the go-to option since it is the safest. This can be expensive if there are many records to destroy.
|
9
9
|
|
10
|
-
|
10
|
+
It is also useful since a model's associations are rarely updated, but it's business logic can change frequently. This means that if callbacks are added or removed on the associated model, the `dependent` option on the parent model's association may need to be updated to reflect this. Using `dependent: :auto` will automatically select the appropriate `dependent` option based on the current state of the model.
|
11
11
|
|
12
12
|
**NOTE**: The `:auto` option **ONLY** decides between `:destroy` and `:delete` / `:delete_all`. It does not use any of the other `dependent` options:
|
13
13
|
- `:nullify`
|
@@ -17,6 +17,8 @@ If you're looking for a solution with little less magic, check out https://githu
|
|
17
17
|
|
18
18
|
**NOTE**: If for some reason the `:auto` option is unable to decide between `:destroy` and `:delete` / `:delete_all`, it will default to `:destroy`.
|
19
19
|
|
20
|
+
**INFO**: If you're looking for a solution with a little less magic, check out the `incorrect_dependent_option` detector provided by https://github.com/gregnavis/active_record_doctor.
|
21
|
+
|
20
22
|
## Installation
|
21
23
|
|
22
24
|
Install the gem and add it to the application's Gemfile by executing:
|
metadata
CHANGED
@@ -1,14 +1,14 @@
|
|
1
1
|
--- !ruby/object:Gem::Specification
|
2
2
|
name: dependent-auto-rails
|
3
3
|
version: !ruby/object:Gem::Version
|
4
|
-
version: 0.2.
|
4
|
+
version: 0.2.2
|
5
5
|
platform: ruby
|
6
6
|
authors:
|
7
7
|
- Joshua Young
|
8
8
|
autorequire:
|
9
9
|
bindir: bin
|
10
10
|
cert_chain: []
|
11
|
-
date: 2024-03-
|
11
|
+
date: 2024-03-03 00:00:00.000000000 Z
|
12
12
|
dependencies:
|
13
13
|
- !ruby/object:Gem::Dependency
|
14
14
|
name: activerecord
|