apidae 1.4.24 → 1.4.26

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 5e513d29358cb1f27b691b5ed7737a2a150c58401293cad26bd5f16b70b2e9fa
-  data.tar.gz: 5a2b4761a88125484589340bba590cd3c435884d34d517ed9997388f74b25420
+  metadata.gz: 1b5f1e7bc931578067144a5f16694fbc79e2f51c467656b2b1dcaf9fcc34b632
+  data.tar.gz: 70357a305970c3bc87e9a235ba1343cccb9d7f05fdcef6c87dd41087fb451e08
 SHA512:
-  metadata.gz: dee928ac46fc6a92783a01d0c5b93dff176bfcfe4865c06317e271767ad9ed2aa1252b48c5875cfb05e000d4b5f23aed17d2539df4bda648089f3e39bb16ce07
-  data.tar.gz: 13b2bf26534e8de01de8cadd47e60a8f658a0f7de8ed7d1f0c290aca51f1cb08767248e242a054c45225aa22a4fa0f619fc8f7850a0b27e45f29e7755f897cb4
+  metadata.gz: 4e33789e716ab48e998bb58b9daba74c9bb2d02a5208635a2ed4270fb7d8c76a89c43c00f23395e21919d38186164edaf1a56af9373f31e45f81d31ed79a71c3
+  data.tar.gz: 1d19cf480d60561f29554334b6b6ab14778750e6048555cd4b262b533e3c472f4c0bbe91847af12bcc2d8d564e97b16c103a81910a8b6215ceb320bc81c2808a

data/app/models/apidae/apidae_data_parser.rb

@@ -179,13 +179,21 @@ module Apidae
           case c[:type][:id]
           when PHONE, ALT_PHONE
             contact_details[:telephone] ||= {}
-            contact_details[:telephone][c[:identifiant]] = {value: c[:coordonnees][:fr], description: c.dig(:observation, :libelleFr)}
+            contact_details[:telephone][c[:identifiant]] = {
+              value: c.dig(:coordonnees, :fr),
+              description: c.dig(:observation, :libelleFr),
+              locales: Hash[(c[:coordonnees] || {}).except(:fr).keys.map {|l| [l, {value: c.dig(:coordonnees, l), description: c.dig(:observation, localized_key(l.to_s))}]}]
+            }
           else
             contacts_refs_by_code = CONTACTS_MAP.invert
             if contacts_refs_by_code.keys.include?(c[:type][:id])
               contact_ref = contacts_refs_by_code[c[:type][:id]].to_sym
               contact_details[contact_ref] ||= {}
-              contact_details[contact_ref][c[:identifiant]] = {value: c[:coordonnees][:fr], description: c.dig(:observation, :libelleFr)}
+              contact_details[contact_ref][c[:identifiant]] = {
+                value: c.dig(:coordonnees, :fr),
+                description: c.dig(:observation, :libelleFr),
+                locales: Hash[(c[:coordonnees] || {}).except(:fr).keys.map {|l| [l, {value: c.dig(:coordonnees, l), description: c.dig(:observation, localized_key(l.to_s))}]}]
+              }
             end
           end
         end

data/lib/apidae/version.rb

@@ -1,3 +1,3 @@
 module Apidae
-  VERSION = "1.4.24"
+  VERSION = "1.4.26"
 end

data/test/dummy/log/development.log

@@ -15128,6 +15128,78 @@ callback this way:
 That block runs when the application boots, and every time there is a reload.
 For historical reasons, it may run twice, so it has to be idempotent.
 
+Check the "Autoloading and Reloading Constants" guide to learn more about how
+Rails autoloads and reloads.
+ (called from <top (required)> at /Users/jbvilain/workspace/code/apidae-engine-rails/test/dummy/config/environment.rb:5)
+DEPRECATION WARNING: Initialization autoloaded the constants Apidae::ApidaeHelper, Apidae::ApplicationHelper, Apidae::ApiHelper, Apidae::DashboardHelper, Apidae::ExtendableHelper, Apidae::ImportHelper, Apidae::ObjectsHelper, Apidae::ReferencesHelper, Apidae::SelectionsHelper, and Apidae::ApplicationController.
+
+Being able to do this is deprecated. Autoloading during initialization is going
+to be an error condition in future versions of Rails.
+
+Reloading does not reboot the application, and therefore code executed during
+initialization does not run again. So, if you reload Apidae::ApidaeHelper, for example,
+the expected changes won't be reflected in that stale Module object.
+
+`config.autoloader` is set to `classic`. These autoloaded constants would have been unloaded if `config.autoloader` had been set to `:zeitwerk`.
+
+In order to autoload safely at boot time, please wrap your code in a reloader
+callback this way:
+
+    Rails.application.reloader.to_prepare do
+      # Autoload classes and modules needed at boot time here.
+    end
+
+That block runs when the application boots, and every time there is a reload.
+For historical reasons, it may run twice, so it has to be idempotent.
+
+Check the "Autoloading and Reloading Constants" guide to learn more about how
+Rails autoloads and reloads.
+ (called from <top (required)> at /Users/jbvilain/workspace/code/apidae-engine-rails/test/dummy/config/environment.rb:5)
+DEPRECATION WARNING: Initialization autoloaded the constants Apidae::ApidaeHelper, Apidae::ApplicationHelper, Apidae::ApiHelper, Apidae::DashboardHelper, Apidae::ExtendableHelper, Apidae::ImportHelper, Apidae::ObjectsHelper, Apidae::ReferencesHelper, Apidae::SelectionsHelper, and Apidae::ApplicationController.
+
+Being able to do this is deprecated. Autoloading during initialization is going
+to be an error condition in future versions of Rails.
+
+Reloading does not reboot the application, and therefore code executed during
+initialization does not run again. So, if you reload Apidae::ApidaeHelper, for example,
+the expected changes won't be reflected in that stale Module object.
+
+`config.autoloader` is set to `classic`. These autoloaded constants would have been unloaded if `config.autoloader` had been set to `:zeitwerk`.
+
+In order to autoload safely at boot time, please wrap your code in a reloader
+callback this way:
+
+    Rails.application.reloader.to_prepare do
+      # Autoload classes and modules needed at boot time here.
+    end
+
+That block runs when the application boots, and every time there is a reload.
+For historical reasons, it may run twice, so it has to be idempotent.
+
+Check the "Autoloading and Reloading Constants" guide to learn more about how
+Rails autoloads and reloads.
+ (called from <top (required)> at /Users/jbvilain/workspace/code/apidae-engine-rails/test/dummy/config/environment.rb:5)
+DEPRECATION WARNING: Initialization autoloaded the constants Apidae::ApidaeHelper, Apidae::ApplicationHelper, Apidae::ApiHelper, Apidae::DashboardHelper, Apidae::ExtendableHelper, Apidae::ImportHelper, Apidae::ObjectsHelper, Apidae::ReferencesHelper, Apidae::SelectionsHelper, and Apidae::ApplicationController.
+
+Being able to do this is deprecated. Autoloading during initialization is going
+to be an error condition in future versions of Rails.
+
+Reloading does not reboot the application, and therefore code executed during
+initialization does not run again. So, if you reload Apidae::ApidaeHelper, for example,
+the expected changes won't be reflected in that stale Module object.
+
+`config.autoloader` is set to `classic`. These autoloaded constants would have been unloaded if `config.autoloader` had been set to `:zeitwerk`.
+
+In order to autoload safely at boot time, please wrap your code in a reloader
+callback this way:
+
+    Rails.application.reloader.to_prepare do
+      # Autoload classes and modules needed at boot time here.
+    end
+
+That block runs when the application boots, and every time there is a reload.
+For historical reasons, it may run twice, so it has to be idempotent.
+
 Check the "Autoloading and Reloading Constants" guide to learn more about how
 Rails autoloads and reloads.
  (called from <top (required)> at /Users/jbvilain/workspace/code/apidae-engine-rails/test/dummy/config/environment.rb:5)

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: apidae
 version: !ruby/object:Gem::Version
-  version: 1.4.24
+  version: 1.4.26
 platform: ruby
 authors:
 - Jean-Baptiste Vilain
 autorequire:
 bindir: bin
 cert_chain: []
-date: 2026-06-11 00:00:00.000000000 Z
+date: 2026-06-16 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: rails