apidae 1.2.32 → 1.2.33

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 3fcd6ed7fe68248f1afd25dac542413aacf16dc7215d754a88eca43621d28ddd
-  data.tar.gz: cf90c2756612c64ed15082e8b3e8fc3b83f32c01d2647aa766f45e8cdf562c87
+  metadata.gz: 4b734a86f74580f550511355efe321a11d760d140c9bfcc42bca846ea30706a4
+  data.tar.gz: 696d2b99eed6646d84320f239a7edb94edb3e2f6faa7b82891d90e7c8bf7d95a
 SHA512:
-  metadata.gz: 2be47f19c21d082da47bea33780d7d6e0e40636964901b566aa7e9d37bd68dfba14a39978f76a27b9a5ed94f6bbea932577c5f00f54d7a1e7accf27254dbe070
-  data.tar.gz: 5c015959607afd5f57c188b31934b635c0042d2f0e1ff52ff3fc471b70b79f3f78d8edf3edb89a9360757226c0741b8e36e450322c0e0991b0b101b7950a49b9
+  metadata.gz: 97545275be12c00ba5c803a624b7c5f35efa1121405acb7b3059cdc8795de97cf3ff51225eb1e26d032459fbd4cca3a8509e37496c4b021b645fbf865f042268
+  data.tar.gz: 6b44066754d0a2010b6cf5301ab61f337974f1dbde0739dce1fef461bafe8d9a8cb1d5354b179c3a08faaf72873080128b6f0561963f41198650c89257839a0d

data/app/models/apidae/apidae_data_parser.rb

@@ -362,7 +362,10 @@ module Apidae
       entity_hash = {}
       if information_hash
         if information_hash[:structureGestion]
-          entity_hash.merge!({entity_id: information_hash[:structureGestion][:id], service_provider_id: node_id(type_data_hash, :prestataireActivites)})
+          entity_hash.merge!({entity_id: information_hash[:structureGestion][:id], entity_name: information_hash[:structureGestion][:nom][:libelleFr],
+                              info_entity_id: (information_hash[:structureInformation] || information_hash[:structureGestion])[:id],
+                              info_entity_name: (information_hash[:structureInformation] || information_hash[:structureGestion])[:nom][:libelleFr],
+                              service_provider_id: node_id(type_data_hash, :prestataireActivites)})
         end
 
         if information_hash[:informationsLegales]

data/app/models/apidae/obj.rb

@@ -17,7 +17,7 @@ module Apidae
     store_accessor :type_data, :categories, :themes, :capacity, :classification, :classification_date,
                    :classification_ref, :labels, :chains, :area, :track, :tricky_sections, :products, :audience, :animals,
                    :animals_desc, :extra, :duration, :certifications, :business, :business_equipments, :business_rooms
-    store_accessor :entity_data, :entity_id, :entity_name, :service_provider_id, :is_service_provider, :legal
+    store_accessor :entity_data, :entity_id, :entity_name, :info_entity_id, :info_entity_name, :service_provider_id, :is_service_provider, :legal
     store_accessor :contact_data, :telephone, :email, :website, :google, :facebook, :twitter, :yelp, :trip_advisor, :fax,
                    :mobile_website, :shorty_url, :contacts
     store_accessor :location_data, :address, :place, :latitude, :longitude, :access, :territories, :environments, :altitude, :map_reference

data/lib/apidae/version.rb

@@ -1,3 +1,3 @@
 module Apidae
-  VERSION = "1.2.32"
+  VERSION = "1.2.33"
 end

data/test/dummy/log/development.log

@@ -19,177 +19,19 @@ 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/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)
-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)
-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)
+  Apidae::Obj Load (0.8ms)  SELECT "apidae_objs".* FROM "apidae_objs" WHERE "apidae_objs"."root_obj_id" IS NULL ORDER BY "apidae_objs"."id" ASC LIMIT $1  [["LIMIT", 1]]
+  TRANSACTION (1.0ms)  BEGIN
+  Apidae::Obj Create (8.3ms)  INSERT INTO "apidae_objs" ("apidae_type", "created_at", "updated_at", "description_data") VALUES ($1, $2, $3, $4) RETURNING "id"  [["apidae_type", "test"], ["created_at", "2023-02-16 21:12:52.351303"], ["updated_at", "2023-02-16 21:12:52.351303"], ["description_data", "{\"short_desc\":{\"\":\"test desc\"}}"]]
+  TRANSACTION (0.7ms)  COMMIT
+  TRANSACTION (0.2ms)  BEGIN
+  Apidae::Obj Update (1.3ms)  UPDATE "apidae_objs" SET "updated_at" = $1, "description_data" = $2 WHERE "apidae_objs"."id" = $3  [["updated_at", "2023-02-16 21:16:00.968796"], ["description_data", "{\"short_desc\":{\"\":\"test desc\",\"fr\":\"updated desc\"}}"], ["id", 1]]
+  TRANSACTION (0.7ms)  COMMIT
+  TRANSACTION (0.2ms)  BEGIN
+  Apidae::Obj Create (0.9ms)  INSERT INTO "apidae_objs" ("apidae_type", "created_at", "updated_at", "description_data") VALUES ($1, $2, $3, $4) RETURNING "id"  [["apidae_type", "HOTELLERIE"], ["created_at", "2023-02-16 21:17:36.422310"], ["updated_at", "2023-02-16 21:17:36.422310"], ["description_data", "{\"short_desc\":{\"fr\":\"short desc fr\"}}"]]
+  TRANSACTION (1.4ms)  COMMIT
 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