store_model 1.3.0 → 1.4.0
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- checksums.yaml +4 -4
- data/README.md +6 -8
- data/lib/store_model/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: 04d0447a36db9c3cec8c6636e0480c188d5d1f70011485dc8aad3aef17979fe5
|
4
|
+
data.tar.gz: ab7835f6a2fa0e3d481a92c9dd94f7946f0da2d788f665faefe8196d141d57e4
|
5
5
|
SHA512:
|
6
|
-
metadata.gz:
|
7
|
-
data.tar.gz:
|
6
|
+
metadata.gz: 271ef39c6e35da560a31646b0731f25daa56005ae955c42c40236befbc98bfb3479e233f84cbabc4a40d299c65812bbc752b55e4e9350f65aaaea89cf5c8e0ac
|
7
|
+
data.tar.gz: a5da18d298f3c254b0f0f2d38075953077a601fc4589df632d6d31222338b12f808cfecc5138d1916a34bf6aa67da96bb71535bb74fa3989a31df44e013d9305
|
data/README.md
CHANGED
@@ -1,4 +1,4 @@
|
|
1
|
-
# StoreModel [](https://rubygems.org/gems/store_model) [](https://coveralls.io/github/DmitryTsepelev/store_model?branch=master)
|
1
|
+
# StoreModel [](https://rubygems.org/gems/store_model) [](https://coveralls.io/github/DmitryTsepelev/store_model?branch=master) 
|
2
2
|
|
3
3
|
**StoreModel** gem allows you to wrap JSON-backed DB columns with ActiveModel-like classes.
|
4
4
|
|
@@ -22,12 +22,6 @@ class Product < ApplicationRecord
|
|
22
22
|
end
|
23
23
|
```
|
24
24
|
|
25
|
-
<p align="center">
|
26
|
-
<a href="https://evilmartians.com/?utm_source=store_model">
|
27
|
-
<img src="https://evilmartians.com/badges/sponsored-by-evil-martians.svg" alt="Sponsored by Evil Martians" width="236" height="54">
|
28
|
-
</a>
|
29
|
-
</p>
|
30
|
-
|
31
25
|
## Why should I wrap my JSON columns?
|
32
26
|
|
33
27
|
Imagine that you have a model `Product` with a `jsonb` column called `configuration`. This is how you likely gonna work with this column:
|
@@ -42,7 +36,7 @@ product.save
|
|
42
36
|
|
43
37
|
This approach works fine when you don't have a lot of keys with logic around them and just read the data. However, when you start working with that data more intensively–you may find the code a bit verbose and error-prone.
|
44
38
|
|
45
|
-
For instance, try to find a way to validate `:model` value to be required. Despite of the fact, that you'll have to write this validation by hand, it violates single-
|
39
|
+
For instance, try to find a way to validate `:model` value to be required. Despite of the fact, that you'll have to write this validation by hand, it violates the single-responsibility principle: why parent model (`Product`) should know about the logic related to a child (`Configuration`)?
|
46
40
|
|
47
41
|
> 📖 Read more about the motivation in the [Wrapping JSON-based ActiveRecord attributes with classes](https://evilmartians.com/chronicles/wrapping-json-based-active-record-attributes-with-classes) post
|
48
42
|
|
@@ -97,6 +91,10 @@ _Usage note: Rails and assigning Arrays/Hashes to records_
|
|
97
91
|
4. [Alternatives](./docs/alternatives.md)
|
98
92
|
5. [Defining custom types](./docs/defining_custom_types.md)
|
99
93
|
|
94
|
+
## Credits
|
95
|
+
|
96
|
+
Initially sponsored by [Evil Martians](http://evilmartians.com).
|
97
|
+
|
100
98
|
## License
|
101
99
|
|
102
100
|
The gem is available as open source under the terms of the [MIT License](https://opensource.org/licenses/MIT).
|
data/lib/store_model/version.rb
CHANGED
metadata
CHANGED
@@ -1,14 +1,14 @@
|
|
1
1
|
--- !ruby/object:Gem::Specification
|
2
2
|
name: store_model
|
3
3
|
version: !ruby/object:Gem::Version
|
4
|
-
version: 1.
|
4
|
+
version: 1.4.0
|
5
5
|
platform: ruby
|
6
6
|
authors:
|
7
7
|
- DmitryTsepelev
|
8
8
|
autorequire:
|
9
9
|
bindir: bin
|
10
10
|
cert_chain: []
|
11
|
-
date:
|
11
|
+
date: 2023-01-16 00:00:00.000000000 Z
|
12
12
|
dependencies:
|
13
13
|
- !ruby/object:Gem::Dependency
|
14
14
|
name: activerecord
|