quickery 1.3.0 → 1.3.1

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: ef98d8559e4364a5532777fc264d895dab630d914475bf663978798f5fce932c
-  data.tar.gz: ab4eda789c789b451d68a7839e508aef9a4178c039c250207a79d85e09b97ccf
+  metadata.gz: c66956aa25df98d05f2a57795491d0752c487c8b0c736f2c5e6401f9ac2f1cf5
+  data.tar.gz: 0c75a721763dc9fec3d0bbb724256460b166c491d44c3f834a2b396514806cf2
 SHA512:
-  metadata.gz: 62d2462169148384f2bdd6675bfbbc70a0fc5908b63be6c0e14726f75ac678c083e8c9fa8621f4decb857074d130724c9e7ff7b417f0d5e32e2f92a815ee33e5
-  data.tar.gz: 57f167d27cf38b2b4e1753f3ec6fbf81843d6f67e452310041f16acf63daba26ca9202ccc64bda393cca3e1ea30f3acbe6da57ec6b1a6e46b7cb7eedbcd7d1ba
+  metadata.gz: 0c3746a7897a5bb8c0ddd8366ea3b2fe071361b9cb42da6d1b81b76b759a4b360e15ff981b03eb96bab0bb5c8324c0ab48c2fc00bf367e1452cdf46e31891332
+  data.tar.gz: 30b3a208a589582dc377dd1c348f243627d3539ead5f4de17e97a956c732347aedc93e79807e262fa8afeb841eaa95149f3a32117fad2f7ca1ef5b3c3bf21ac4

data/README.md

@@ -432,7 +432,7 @@ class AddQuickeryBranchCompanyNameBranchCompanyIdToEmployees < ActiveRecord::Mig
 end
 ```
 
-#### Example 2
+#### Example 2 - With `*_is_synced` Attributes
 
 ```
 rails generate quickery:migration employee branch_company_name:string branch_company_id:bigint:index --add_is_synced_attributes
@@ -512,10 +512,10 @@ end
     ```
 
 ##### `autoload_unsynced_quickery_attributes!`
-* only works in conjuction with `*_is_synced` attributes.
+* only works in conjuction with `*_is_synced` attributes. See Usage Example 3 above.
 * this will update the record's "still unsynced" quickery-attributes.
 * if all of the record's quickery-attributes are already "synced", then this method does nothing more
-* intended to be used as callback method for `after_find` to automatically support both 1) "old-records" that before quickery has been integrated, and 2) new quickery-attributes to be defined in the future
+* intended to be used as callback method for `after_find` to automatically support both 1) "old-records" created before quickery has been integrated, and 2) new quickery-attributes to be defined in the future
 * i.e. you can do something like the following:
 
     ```ruby
@@ -563,6 +563,8 @@ See [my detailed comparisons](other_similar_gems_comparison.md)
 5. Create new Pull Request
 
 ## Changelog
+* 1.3.1
+  * Fix error from 1.3.0 where private method was being called outside class
 * 1.3.0
   * implemented tracking of which quickery-attributes have already been synced / not yet via additional optional `*_is_synced` attributes; used in conjuction with [`autoload_unsynced_quickery_attributes!`](#autoload_unsynced_quickery_attributes) intentionally to be declared as callback method for `after_find`, which will make sure that new quickery-attributes defined in the future will work immediately for the record, and that the developer won't worry about doing the `recreate_quickery_cache!` anymore, as the record is guaranteed to be always up-to-date.
 * 1.2.0

data/lib/quickery/active_record_extensions/dsl.rb

@@ -19,8 +19,6 @@ module Quickery
           mappings_builder.map_attributes
         end
 
-        private
-
         # subclass overrideable
         def quickery_before_create_or_update(dependent_record, new_values)
           dependent_record.assign_attributes(new_values)

data/lib/quickery/version.rb

@@ -1,3 +1,3 @@
 module Quickery
-  VERSION = '1.3.0'
+  VERSION = '1.3.1'
 end

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: quickery
 version: !ruby/object:Gem::Version
-  version: 1.3.0
+  version: 1.3.1
 platform: ruby
 authors:
 - Jules Roman Polidario