airtable-orm 0.2.1 → 0.2.3

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: dc3056cbf98026ea8a89b01d99c632ad01da304d85841544552b44565f897793
-  data.tar.gz: cf839f12c5812c4834604dc46c716fdb671c47110d94829fa863d82f5d56e489
+  metadata.gz: 628a8ae1f053bb9b1f598608785b9a09062797d152e234d7cd2e2b1a4fefb982
+  data.tar.gz: 30813eda1cfb49e6e74418be674490526697264c3d67b6d6f6edd0d3f194c810
 SHA512:
-  metadata.gz: dfcd829b2a0df28d151770f30c0f51e98680bc6ab0c6f8fd5f0ff9fd2fd6ffefdef4f3c30fbe7dbcb3f3afa08689d6dffb6fc234d28a4403c3ec56f004f0abfa
-  data.tar.gz: 6c31d239c24e6c86e6303cc5eb7fdd34a5916c914c27999625c6b0c945178f9d7def6386855ba77cc13493054d14dc8abf1f087ca27474b8ff6a21f1e34f2e57
+  metadata.gz: ba0c3abab62e8f8931c6f7ca3f84fe35b343e5341df5ea9652f641c1b8b6d146241be1cd3b554d84232b2d44a1651c475aee2f5abb8580a4b75b2faf9c971806
+  data.tar.gz: 3394db605f8b6910d0e41a40c9087ba74daa36b3b5b60d5db65487fa870d4dbc4e0c56c4aed43d5476473e327fc7cf6bd9b6856078578a6809d78b9bc6a5fc49

data/CHANGELOG.md

@@ -1,5 +1,28 @@
 ## [Unreleased]
 
+## [0.2.3] - 2026-09-24
+
+### Fixed
+
+- Require `faraday >= 2.14.4` (was `~> 2.9`). Older Faraday releases can't parse responses
+  once the host resolves json 3.0 (released 2026-09-09): every request raises
+  `Faraday::ParsingError: wrong number of arguments`. This affects every earlier airtable-orm
+  release, which all allowed any Faraday 2.9+.
+
+## [0.2.2] - 2026-09-24
+
+### Fixed
+
+- `find` raises `RecordNotFound` for a deleted/nonexistent record ID. Airtable answers such a
+  GET with `403 INVALID_PERMISSIONS_OR_MODEL_NOT_FOUND`, not 404, so it used to surface as a
+  plain `ApiError`. Because a revoked token or lost table permission returns the same 403, `find`
+  now disambiguates with one probe of the table (a one-record, no-fields list request): readable
+  → `RecordNotFound`, otherwise the original `ApiError` is re-raised; a `ConnectionError` during
+  the probe propagates. The 404 mapping is unchanged. `reload` and `belongs_to` (which reads a
+  stale link as `nil`) benefit accordingly.
+- `ApiError` is raised (instead of a `TypeError`) for Airtable's bare string error body such as
+  `{"error": "NOT_FOUND"}`, which previously broke the 404 → `RecordNotFound` mapping in `find`.
+
 ## [0.2.1] - 2026-07-15
 
 ### Fixed

data/lib/airtable/orm/http/client.rb

@@ -66,11 +66,13 @@ module Airtable
           ERB::Util.url_encode(string)
         end
 
-        # Parse an Airtable API error response and raise an ApiError.
+        # Parse an Airtable API error response and raise an ApiError. Airtable sends either
+        # {"error" => {"type", "message"}} or a bare {"error" => "NOT_FOUND"} (e.g. on 404).
         def self.raise_api_error(status, error)
-          type = (error.is_a?(Hash) && error.dig("error", "type")) || "Communication error"
+          detail = error.is_a?(Hash) ? error["error"] : nil
+          type = (detail.is_a?(Hash) ? detail["type"] : detail) || "Communication error"
           msg = case error
-                when Hash then error.dig("error", "message")
+                when Hash then detail.is_a?(Hash) ? detail["message"] : nil
                 when String then error
                 when NilClass then "invalid or empty response body (not valid JSON)"
                 else error.inspect

data/lib/airtable/orm/persistence.rb

@@ -74,7 +74,9 @@ module Airtable
             Airtable::ORM::Http::Client.raise_api_error(response.status, parsed_response)
           end
         rescue Airtable::ORM::ApiError => e
-          raise Airtable::ORM::RecordNotFound, "Couldn't find record with id=#{id}" if e.status == 404
+          if e.status == 404 || (missing_record_forbidden?(e) && table_readable?)
+            raise Airtable::ORM::RecordNotFound, "Couldn't find record with id=#{id}"
+          end
 
           raise
         end
@@ -145,6 +147,22 @@ module Airtable
 
         private
 
+        # Airtable answers a GET for a nonexistent (e.g. deleted) record ID with this 403, not
+        # 404 — the same response a token without access to the table/base gets.
+        def missing_record_forbidden?(error)
+          error.status == 403 && error.response.is_a?(Hash) &&
+            error.response.dig("error", "type") == "INVALID_PERMISSIONS_OR_MODEL_NOT_FOUND"
+        end
+
+        # Disambiguates that 403 with one cheap list request (one record, no fields): readable
+        # table → the record is gone. Never map the 403 blindly — a revoked token or lost
+        # permission would then look like "every record deleted" to the host. A ConnectionError
+        # still propagates (retryable, not evidence either way).
+        def table_readable?
+          response = client.connection.post(api_path("listRecords"), { maxRecords: 1, fields: [] })
+          response.success?
+        end
+
         # Send a single batch PATCH request to Airtable.
         def send_batch_update(batch, result)
           body = {

data/lib/airtable/orm/version.rb

@@ -2,6 +2,6 @@
 
 module Airtable
   module ORM
-    VERSION = "0.2.1"
+    VERSION = "0.2.3"
   end
 end

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: airtable-orm
 version: !ruby/object:Gem::Version
-  version: 0.2.1
+  version: 0.2.3
 platform: ruby
 authors:
 - Roman Sklenar
@@ -35,14 +35,20 @@ dependencies:
     requirements:
     - - "~>"
       - !ruby/object:Gem::Version
-        version: '2.9'
+        version: '2.14'
+    - - ">="
+      - !ruby/object:Gem::Version
+        version: 2.14.4
   type: :runtime
   prerelease: false
   version_requirements: !ruby/object:Gem::Requirement
     requirements:
     - - "~>"
       - !ruby/object:Gem::Version
-        version: '2.9'
+        version: '2.14'
+    - - ">="
+      - !ruby/object:Gem::Version
+        version: 2.14.4
 - !ruby/object:Gem::Dependency
   name: faraday-net_http_persistent
   requirement: !ruby/object:Gem::Requirement