super_callbacks 1.3.0 → 1.3.1
Sign up to get free protection for your applications and to get access to all the features.
- checksums.yaml +4 -4
- data/README.md +4 -4
- data/lib/super_callbacks/version.rb +1 -1
- metadata +1 -1
checksums.yaml
CHANGED
@@ -1,7 +1,7 @@
|
|
1
1
|
---
|
2
2
|
SHA1:
|
3
|
-
metadata.gz:
|
4
|
-
data.tar.gz:
|
3
|
+
metadata.gz: da5242fb78c87c35f8c0cd25dfcff261115d23e9
|
4
|
+
data.tar.gz: cf869220b58098dc7796021e8bdafeb73579bc31
|
5
5
|
SHA512:
|
6
|
-
metadata.gz:
|
7
|
-
data.tar.gz:
|
6
|
+
metadata.gz: 55d5dad14d3068d34b6e0ab57e94aac58b40e5a2dcd50b9618e70aed9d12c3c10558edebb0814bef424f5a0ca0e3bcd4002a6029c8cb9eff69b5be549d42dc7c
|
7
|
+
data.tar.gz: 2fc2a2dc1fd59133b0dbbb2c518f15301c9c2e61f119ee4cdfe1519267ca3941793a64da2e1a2e2d574a4d8181b7cac07d18fadd48bea38a138cc418ae5ca385
|
data/README.md
CHANGED
@@ -144,7 +144,7 @@ foo.bar
|
|
144
144
|
# => 'bar!'
|
145
145
|
```
|
146
146
|
|
147
|
-
*Notice above multiple callbacks are supported, and that they are called in
|
147
|
+
*Notice above multiple callbacks are supported, and that they are called in first-come-first-served order.*
|
148
148
|
|
149
149
|
*Above uses `before`, but works similarly with `after`*
|
150
150
|
|
@@ -407,7 +407,7 @@ foo.bar = 1 # bar is not changed from 1 to 1
|
|
407
407
|
|
408
408
|
## TODOs
|
409
409
|
* when the need already arises, implement `around` (If you have ideas or want to help this part, please feel free to fork or send me a message! :)
|
410
|
-
*
|
410
|
+
* Without changing the DSL, try to find a better solution than current one to fix [this bug](https://github.com/jrpolidario/super_callbacks/issues/1). As it required me to write a bit of overhead code via `InheritancePrepender` module.
|
411
411
|
|
412
412
|
## Development
|
413
413
|
|
@@ -425,8 +425,8 @@ The gem is available as open source under the terms of the [MIT License](https:/
|
|
425
425
|
|
426
426
|
## Changelog
|
427
427
|
|
428
|
-
* [1.3.
|
429
|
-
* [Fixed difficult bug: callbacks not in order when method defined in subclass and not in superclass when using inherited callbacks](https://github.com/jrpolidario/super_callbacks/issues/1
|
428
|
+
* [1.3.1 (2019-08-15)](https://github.com/jrpolidario/super_callbacks/commit/dcc71648d9be06074280c936add04b6b3f921e10)
|
429
|
+
* [Fixed difficult bug: callbacks not in order when method defined in subclass and not in superclass when using inherited callbacks](https://github.com/jrpolidario/super_callbacks/issues/1)
|
430
430
|
* Refactored a lot of code, and added slight overhead. I'm satisfied at the moment until I could find the best solution.
|
431
431
|
* 1.2.0 (2019-08-15)
|
432
432
|
* [Fixed / Supported Nested "Dirty" Changes on nested callbacks for idempotency (Thread-safe)](https://github.com/jrpolidario/super_callbacks/blob/4e9284e1c6150c6d5da536766d51b4e635bb819d/spec/super_callbacks_spec.rb#L487)
|