rest-easy 1.4.1 → 1.4.2

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: a30780e0b38e31f1c183d1ec0a91ea93658a78e67d2415aeb8aef279d03359b7
-  data.tar.gz: 2ed7aafbcaf5e0c6fd463992a65293d1f064c693611f64b9b3256e8e4b518fdf
+  metadata.gz: a192d482f07dc654cae8267e3166742ee45d90c4bf960f54f632f94ca11c20a6
+  data.tar.gz: 74b41469d03fb34c19616774f9ccb97dfd3191f937dfcf2e96560986333ccf12
 SHA512:
-  metadata.gz: 3ac9ea37e26b652d5fe590075d7668f70e2cf8b7290b02d7e4dd1f227bf7a7e26ea9e5faa02ed1b84b5706262d90e774db52381ea0ce2d026da40d410ae38c11
-  data.tar.gz: 8f8773d0cbacc6366daade22ceee18ee76de91ee5eb5cd718c392e0abfe1ed3a911658a867dab1bcd1f21b077f2296e0cb5ffbb1aa5597f6fee7e77a7b40b84d
+  metadata.gz: b493ff7a6f39fa303665e6e09174b2f664d35960e18864dbb39e3d2cf95fe3ea13543f4384fc3a4c4656d8ada2b029f486ccf99ac6e2d9dda983c74e05717f6b
+  data.tar.gz: fdec9a5343a0bf002fe43b1532849ec7a28520ee95392e4beddcd0e11af1b3fd2ec0c9c2c11eceeafb65ea8dd640281fe521f1613022bc43f60615ca0afc1095

data/CHANGELOG.md

@@ -2,6 +2,34 @@
 
 ## [Unreleased]
 
+## [1.4.2] - 2026-09-23
+
+### Fixed
+
+- **`update` no longer discards state it should carry forward.** It rebuilt
+  the instance's metadata and its change set from scratch instead of
+  inheriting them, which broke three things at once:
+
+  - An instance that had never been saved came back marked as persisted, so
+    `save` took the update branch: a PUT to the collection path with no id in
+    it, for a record the API has never seen, instead of a POST that creates
+    one. Building a record and adjusting it before the first save is the
+    ordinary way to use an immutable resource, and it could not produce a
+    correct create request.
+  - Chained updates kept only the last call's fields. After
+    `a.update(x: 1).update(y: 2)`, `__changes__` reported just `y` while `x`
+    read back as `1` on the instance, so a partial payload built from the
+    change set left out a field the object claimed to carry, and nothing
+    raised.
+  - Metadata set by a `before_parse` hook lives on the instance, not the
+    class, and was dropped. A consumer flagging parsed instances — to mark
+    the thin records a collection endpoint returns, say — lost the flag as
+    soon as anything called `update`.
+
+  `update` now inherits the receiver's metadata and merges its change set.
+  The metadata is copied rather than shared, so mutating an updated copy's
+  metadata still cannot reach the original's.
+
 ## [1.4.1] - 2026-08-18
 
 ### Fixed
@@ -167,7 +195,8 @@
 
 Initial release.
 
-[Unreleased]: https://github.com/accodeing/rest-easy/compare/v1.4.1...HEAD
+[Unreleased]: https://github.com/accodeing/rest-easy/compare/v1.4.2...HEAD
+[1.4.2]: https://github.com/accodeing/rest-easy/compare/v1.4.1...v1.4.2
 [1.4.1]: https://github.com/accodeing/rest-easy/compare/v1.4.0...v1.4.1
 [1.4.0]: https://github.com/accodeing/rest-easy/compare/v1.3.1...v1.4.0
 [1.3.1]: https://github.com/accodeing/rest-easy/compare/v1.3.0...v1.3.1

data/lib/rest_easy/meta.rb

@@ -6,6 +6,11 @@ module RestEasy
       @data = { new: new_record, saved: saved, **defaults }
     end
 
+    def initialize_copy(source)
+      super
+      @data = @data.dup
+    end
+
     def new?
       @data[:new]
     end

data/lib/rest_easy/resource.rb

@@ -598,7 +598,7 @@ module RestEasy
 
       new_model = @model_attributes.merge(coerced)
       new_instance = self.class.allocate
-      new_instance.send(:init_from_update, new_model, @api_data, coerced)
+      new_instance.send(:init_from_update, new_model, @api_data, __changes__.merge(coerced), @meta)
       new_instance
     end
 
@@ -801,11 +801,14 @@ module RestEasy
       end
     end
 
-    def init_from_update(new_model_attrs, original_api_data, changes)
+    def init_from_update(new_model_attrs, original_api_data, changes, meta)
       @api_data = original_api_data
       @model_attributes = new_model_attrs
       @changes = changes
-      @meta = Meta.new(new_record: false, saved: true, **self.class.metadata)
+      # Carried from the receiver, not rebuilt: an instance that was never
+      # saved stays new, so `save` still POSTs it, and metadata a parse hook
+      # set (which lives on the instance, not the class) survives the update.
+      @meta = meta.dup
     end
   end
 end

data/lib/rest_easy/version.rb

@@ -1,5 +1,5 @@
 # frozen_string_literal: true
 
 module RestEasy
-  VERSION = "1.4.1"
+  VERSION = "1.4.2"
 end

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: rest-easy
 version: !ruby/object:Gem::Version
-  version: 1.4.1
+  version: 1.4.2
 platform: ruby
 authors:
 - Jonas Schubert Erlandsson
@@ -10,7 +10,7 @@ authors:
 autorequire:
 bindir: bin
 cert_chain: []
-date: 2026-08-18 00:00:00.000000000 Z
+date: 2026-09-23 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: dry-types