canon 0.3.25 → 0.3.26

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 542f29d833d2a2b08ebf8121b9bf847e4d30bfb2f86127742aad93ef648b8ab0
-  data.tar.gz: 3d16c5ef20e3b540969c21d185d345a6b4fc6e6c0c548811d9af87d6d1105490
+  metadata.gz: '05685ad043ad0a5465f4e065c26cf35ad1b453511ce347a56e60d5a5153e731f'
+  data.tar.gz: 864587a2ddf54edd3f40d71676882b255904dfe6f46ee41a330ef8117ceddfed
 SHA512:
-  metadata.gz: 83d9046ae33bf10605fd636fa9606aaeb481633c12a374046451cd44988f24c9e022257a85441e4d10babc3a0d01957597313cf02fc6373bee43566ed4af76d9
-  data.tar.gz: d286b0b4358c9ef2a86930ae43fb356cb98a0f475affb6f76cae2140f36145fd440851b481d859af2a7a7ba996033d0719547102d09160a596af610d800301c9
+  metadata.gz: 6e568174aeaf605650e7eb64267afddbe30fd4399b82c032757e60177631b75663b0cf388d16e2fbaddea774ea703cb4c88f3e11ac8307ee1a75a3ea6f6530cc
+  data.tar.gz: 5af9aded692f6b909ffd1eb50bb9e96c851b8ca98844a397ceec11f8a2eede33437f99d4df15a2870beee56954924d2fd1ec061b6cb4523d2204fa07524f0710

data/CLAUDE.md

@@ -145,7 +145,7 @@ Engine A/B testing: `CANON_XML_BACKEND=nokogiri bundle exec rspec` (or `=moxml`
 
 ### YAML Engines
 
-`Canon::YamlBackend` selects the YAML engine: `:psych` (default) or `:yeptris` (FFI over libyeptris, the YAML counterpart of the leptris XML stack — `CANON_YAML_BACKEND=yeptris` opts in; the optional `yeptris` Gemfile group must be enabled). `Canon::YamlParsing` is the single gateway for string loads; `Canon::JsonParsing` mirrors it for JSON (the same yeptris engine serves both — `Yeptris::YAML.load` auto-detects JSON and routes to the native C-API materializer; JSON falls back to stdlib unless `YamlBackend.yeptris_native?`, since the FFI ladder is ~29x slower than the stdlib C extension). `YAML.dump` stays on Psych everywhere — canonical output bytes are canon's product and the writers differ. The default stays `:psych` until the yeptris Psych-parity gaps close (yeptris-ruby#30 sexagesimal scalars, #31 >64-bit integers — #29 empty documents was fixed in 0.1.12); `spec/canon/yaml_engine_parity_spec.rb` is the executable gate, with upstream-tracked cases pending. Never `require "yeptris/psych"` — it rebinds the global `::Psych` constant for the whole process; only the namespaced `Yeptris::YAML` API is used.
+`Canon::YamlBackend` selects the YAML engine: `:psych` (default) or `:yeptris` (FFI over libyeptris, the YAML counterpart of the leptris XML stack — `CANON_YAML_BACKEND=yeptris` opts in; the optional `yeptris` Gemfile group must be enabled). `Canon::YamlParsing` is the single gateway for string loads; `Canon::JsonParsing` mirrors it for JSON (the same yeptris engine serves both — `Yeptris::YAML.load` auto-detects JSON and routes to the native C-API materializer; JSON falls back to stdlib unless `YamlBackend.yeptris_native?`, since the FFI ladder is ~29x slower than the stdlib C extension). `YAML.dump` stays on Psych everywhere — canonical output bytes are canon's product and the writers differ. **JSON defaults to the strict yeptris surface whenever the native materializer is installed** (yeptris 0.1.13.4 ships platform gems — zero compilation, zero env; parity spec-pinned to `JSON.parse` upstream). The YAML default stays `:psych` until the yeptris Psych-parity gaps close (yeptris-ruby#30 sexagesimal scalars, #31 >64-bit integers — #29 empty documents was fixed in 0.1.12); `spec/canon/yaml_engine_parity_spec.rb` is the executable gate, with upstream-tracked cases pending. Never `require "yeptris/psych"` — it rebinds the global `::Psych` constant for the whole process; only the namespaced `Yeptris::YAML` API is used.
 
 ### Format Detection
 

data/lib/canon/json_parsing.rb

@@ -14,7 +14,7 @@ module Canon
     module_function
 
     def parse(json)
-      if Canon::YamlBackend.yeptris_native?
+      if Canon::YamlBackend.json_yeptris?
         begin
           # The strict JSON surface — spec-pinned to exact JSON.parse
           # semantics upstream, deliberately separate from the YAML

data/lib/canon/version.rb

@@ -1,5 +1,5 @@
 # frozen_string_literal: true
 
 module Canon
-  VERSION = "0.3.25"
+  VERSION = "0.3.26"
 end

data/lib/canon/yaml_backend.rb

@@ -59,6 +59,22 @@ module Canon
         yeptris? && yeptris_available? && !defined?(::Yeptris::Native).nil?
       end
 
+      # JSON defaults to the strict yeptris surface whenever the
+      # native materializer is installed (0.1.13.4 ships platform
+      # gems — zero compilation, zero env). JSON parity is
+      # spec-pinned to JSON.parse upstream and complete except the
+      # #37 duplicate-keys leniency; YAML keeps waiting on #30/#31
+      # and stays behind the env opt-in. CANON_YAML_BACKEND=psych
+      # forces both formats back to stdlib.
+      def json_yeptris?
+        return false if RUBY_ENGINE == "opal"
+        return false if ENV["CANON_YAML_BACKEND"].to_s.casecmp("psych").zero?
+
+        # Independent of the YAML selection: the strict JSON surface
+        # is complete on its own, so JSON does not wait for #30/#31.
+        yeptris_available? && !defined?(::Yeptris::Native).nil?
+      end
+
       private
 
       def forced

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: canon
 version: !ruby/object:Gem::Version
-  version: 0.3.25
+  version: 0.3.26
 platform: ruby
 authors:
 - Ribose Inc.