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 CHANGED
@@ -1,7 +1,7 @@
1
1
  ---
2
2
  SHA1:
3
- metadata.gz: a9de4f62f5259330dd9c9043dcd6e9e5faa50bfb
4
- data.tar.gz: 5428ec46f89d68264b01e11d2ab32a9ac076834d
3
+ metadata.gz: da5242fb78c87c35f8c0cd25dfcff261115d23e9
4
+ data.tar.gz: cf869220b58098dc7796021e8bdafeb73579bc31
5
5
  SHA512:
6
- metadata.gz: 7416ac8af83da5407af6113f103b28dee8729086b0e9f2cc53b689252abe4883c23cdaeff553102761a8b5dbf16222d40ca009e0fff5ee273a03eb2633a0e308
7
- data.tar.gz: 3c984287755e49a18b8b5b3e46ee6a95911ca9e7bf5b9e86e922638c4329b73a3d5166264aa62647930d021bdf00e711a8537af78e18838a1bfedbb82148d042
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 firt-come-first-served order.*
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
- * [Found a new bug I could not solve](https://github.com/jrpolidario/super_callbacks/issues/1). If you have any ideas how to solve this, please feel to submit a merge request! :) At the moment, this is not important to me (yet?) as I develop my game engine, so I'm leaving this here for now, and I'll come back again into this later.
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.0 (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
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)
@@ -1,3 +1,3 @@
1
1
  module SuperCallbacks
2
- VERSION = '1.3.0'
2
+ VERSION = '1.3.1'
3
3
  end
metadata CHANGED
@@ -1,7 +1,7 @@
1
1
  --- !ruby/object:Gem::Specification
2
2
  name: super_callbacks
3
3
  version: !ruby/object:Gem::Version
4
- version: 1.3.0
4
+ version: 1.3.1
5
5
  platform: ruby
6
6
  authors:
7
7
  - Jules Roman B. Polidario