active_outbox 0.2.0 → 0.2.2

Sign up to get free protection for your applications and to get access to all the features.
Files changed (3) hide show
  1. checksums.yaml +4 -4
  2. data/README.md +3 -1
  3. metadata +3 -3
checksums.yaml CHANGED
@@ -1,7 +1,7 @@
1
1
  ---
2
2
  SHA256:
3
- metadata.gz: 2d0e31246689108b94262916f2128e1f1085dadb8b75cb62016a23d7c1a23236
4
- data.tar.gz: 50caba92044342c95532737086eaebac4422f9a6fc370c84b75763d28f2360e4
3
+ metadata.gz: d76f50b2bce358c763d6e4ba48b75b0c20764b8d44520e84ec7d6e47fdcec6d7
4
+ data.tar.gz: f391673c6cd58b3a1e23ae2c4b694d75d6d2f203731fb3cda814453b6337f36e
5
5
  SHA512:
6
- metadata.gz: 906a6d7f317a8d178e20852601d3a52a89655e8bca6d72ebd0adb8dda5aca8d7385ab8fe8a9822380274b8e8c3c9a118e2fe14cf2f9e27c5cb926387b8dd0313
7
- data.tar.gz: 3523ac574209865c4e061559a9517a434fb8fb43b37756abf512dc67d309bc6cedd6a870a98212de81325f2b0ab128456c42c0f4a05ee943d35c9d9213c60828
6
+ metadata.gz: 35b5ef496c7a2a50c1967bb1a7f0112a25d6e275c9486f1bfb91eb927b16c579cc259a1f707c749140d817bb974f7e94fbcec73058a3dbd4e00c2de159534c87
7
+ data.tar.gz: 8114e43925215f34ab3ea9ee9022b8c14219d23ca4f4624bbc1b472b3353a815c64ea0ccc858cb32041e0e1b722bad7a1cd738f13afccb289523e3f20f3a177c
data/README.md CHANGED
@@ -63,6 +63,8 @@ Using the User model as an example, the default event names provided are:
63
63
  - USER_UPDATED
64
64
  - USER_DESTROYED
65
65
 
66
+ This will live under `ActiveOutbox::Events` wherever you include the `Outboxable` concern. The intent is to define it under `Object` for non-namespaced models, as well as under each model namespace that is encountered.
67
+
66
68
  ### Custom Events
67
69
  If you want to persist a custom event other than the provided base events, you can do so.
68
70
  ```ruby
@@ -75,7 +77,7 @@ By default our Outbox migration has an `aggregate_identifier` field which serves
75
77
  rails g active_outbox:model <optional model_name> --uuid
76
78
  ```
77
79
  ### Modularized Outbox Mappings
78
- If more granularity is desired multiple outbox classes can be configured. Using the provided generators we can specify namespaces and the folder structure.
80
+ If more granularity is desired multiple outbox classes can be configured. Using the provided generators we can specify namespaces and the folder structure.
79
81
  ```bash
80
82
  rails g active_outbox:model user_access/ --component-path packs/user_access
81
83
 
metadata CHANGED
@@ -1,14 +1,14 @@
1
1
  --- !ruby/object:Gem::Specification
2
2
  name: active_outbox
3
3
  version: !ruby/object:Gem::Version
4
- version: 0.2.0
4
+ version: 0.2.2
5
5
  platform: ruby
6
6
  authors:
7
7
  - Guillermo Aguirre
8
8
  autorequire:
9
9
  bindir: bin
10
10
  cert_chain: []
11
- date: 2024-04-25 00:00:00.000000000 Z
11
+ date: 2024-06-05 00:00:00.000000000 Z
12
12
  dependencies:
13
13
  - !ruby/object:Gem::Dependency
14
14
  name: dry-configurable
@@ -57,7 +57,7 @@ files:
57
57
  - lib/generators/active_outbox/templates/initializer.rb
58
58
  - lib/generators/active_outbox/templates/migration.rb
59
59
  - lib/generators/active_outbox/templates/model.rb
60
- homepage: https://rubygems.org/gems/active_outbox
60
+ homepage: https://github.com/rootstrap/active_outbox
61
61
  licenses:
62
62
  - MIT
63
63
  metadata: {}