trusty-cms 5.0.6 → 5.0.7

data/node_modules/uri-js/tsconfig.json

@@ -1,20 +0,0 @@
-{
-    "compilerOptions": {
-        "module": "es2015",
-        "target": "esnext",
-        "noImplicitAny": true,
-        "sourceMap": true,
-        "alwaysStrict": true,
-        "declaration": true,
-        "experimentalDecorators": true,
-        "forceConsistentCasingInFileNames": true,
-        "importHelpers": true,
-        "noImplicitReturns": true,
-        "noImplicitThis": true,
-        "outDir": "dist/esnext",
-        "strictNullChecks": true
-    },
-    "include": [
-        "src/**/*"
-    ]
-}

data/spec/dummy/log/development.log

@@ -1,456 +0,0 @@
-DEPRECATION WARNING: Initialization autoloaded the constants TrustyCms::Config, Admin, Admin::RegionsHelper, ApplicationHelper, DeviseHelper, ApplicationController, Admin::ResourceHelper, Admin::ResourceController, Admin::LayoutsHelper, Admin::LayoutsController, MultiSite::SiteChooserHelper, Admin::SnippetsController, ActionText::ContentHelper, and ActionText::TagHelper.
-
-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 TrustyCms::Config, for example,
-the expected changes won't be reflected in that stale Class 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/donavin/Documents/development/trusty-cms/spec/dummy/config/environment.rb:5)
-DEPRECATION WARNING: Initialization autoloaded the constants TrustyCms::Config, Admin, Admin::RegionsHelper, ApplicationHelper, DeviseHelper, ApplicationController, Admin::ResourceHelper, Admin::ResourceController, Admin::LayoutsHelper, Admin::LayoutsController, MultiSite::SiteChooserHelper, Admin::SnippetsController, ActionText::ContentHelper, and ActionText::TagHelper.
-
-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 TrustyCms::Config, for example,
-the expected changes won't be reflected in that stale Class 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/donavin/Documents/development/trusty-cms/spec/dummy/config/environment.rb:5)
-DEPRECATION WARNING: Initialization autoloaded the constants TrustyCms::Config, Admin, Admin::RegionsHelper, ApplicationHelper, DeviseHelper, ApplicationController, Admin::ResourceHelper, Admin::ResourceController, Admin::LayoutsHelper, Admin::LayoutsController, MultiSite::SiteChooserHelper, Admin::SnippetsController, ActionText::ContentHelper, and ActionText::TagHelper.
-
-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 TrustyCms::Config, for example,
-the expected changes won't be reflected in that stale Class 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/donavin/Documents/development/trusty-cms/spec/dummy/config/environment.rb:5)
-DEPRECATION WARNING: Initialization autoloaded the constants TrustyCms::Config, Admin, Admin::RegionsHelper, ApplicationHelper, DeviseHelper, ApplicationController, Admin::ResourceHelper, Admin::ResourceController, Admin::LayoutsHelper, Admin::LayoutsController, MultiSite::SiteChooserHelper, Admin::SnippetsController, ActionText::ContentHelper, and ActionText::TagHelper.
-
-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 TrustyCms::Config, for example,
-the expected changes won't be reflected in that stale Class 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/donavin/Documents/development/trusty-cms/spec/dummy/config/environment.rb:5)
-DEPRECATION WARNING: Initialization autoloaded the constants TrustyCms::Config, Admin, Admin::RegionsHelper, ApplicationHelper, DeviseHelper, ApplicationController, Admin::ResourceHelper, Admin::ResourceController, Admin::LayoutsHelper, Admin::LayoutsController, MultiSite::SiteChooserHelper, Admin::SnippetsController, ActionText::ContentHelper, and ActionText::TagHelper.
-
-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 TrustyCms::Config, for example,
-the expected changes won't be reflected in that stale Class 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/donavin/Documents/development/trusty-cms/spec/dummy/config/environment.rb:5)
-DEPRECATION WARNING: Initialization autoloaded the constants TrustyCms::Config, Admin, Admin::RegionsHelper, ApplicationHelper, DeviseHelper, ApplicationController, Admin::ResourceHelper, Admin::ResourceController, Admin::LayoutsHelper, Admin::LayoutsController, MultiSite::SiteChooserHelper, Admin::SnippetsController, ActionText::ContentHelper, and ActionText::TagHelper.
-
-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 TrustyCms::Config, for example,
-the expected changes won't be reflected in that stale Class 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/donavin/Documents/development/trusty-cms/spec/dummy/config/environment.rb:5)
-DEPRECATION WARNING: Initialization autoloaded the constants TrustyCms::Config, Admin, Admin::RegionsHelper, ApplicationHelper, DeviseHelper, ApplicationController, Admin::ResourceHelper, Admin::ResourceController, Admin::LayoutsHelper, Admin::LayoutsController, MultiSite::SiteChooserHelper, Admin::SnippetsController, ActionText::ContentHelper, and ActionText::TagHelper.
-
-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 TrustyCms::Config, for example,
-the expected changes won't be reflected in that stale Class 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/donavin/Documents/development/trusty-cms/spec/dummy/config/environment.rb:5)
-DEPRECATION WARNING: Initialization autoloaded the constants TrustyCms::Config, Admin, Admin::RegionsHelper, ApplicationHelper, DeviseHelper, ApplicationController, Admin::ResourceHelper, Admin::ResourceController, Admin::LayoutsHelper, Admin::LayoutsController, MultiSite::SiteChooserHelper, Admin::SnippetsController, ActionText::ContentHelper, and ActionText::TagHelper.
-
-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 TrustyCms::Config, for example,
-the expected changes won't be reflected in that stale Class 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/donavin/Documents/development/trusty-cms/spec/dummy/config/environment.rb:5)
-DEPRECATION WARNING: Initialization autoloaded the constants TrustyCms::Config, Admin, Admin::RegionsHelper, ApplicationHelper, DeviseHelper, ApplicationController, Admin::ResourceHelper, Admin::ResourceController, Admin::LayoutsHelper, Admin::LayoutsController, MultiSite::SiteChooserHelper, Admin::SnippetsController, ActionText::ContentHelper, and ActionText::TagHelper.
-
-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 TrustyCms::Config, for example,
-the expected changes won't be reflected in that stale Class 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/donavin/Documents/development/trusty-cms/spec/dummy/config/environment.rb:5)
-DEPRECATION WARNING: Initialization autoloaded the constants TrustyCms::Config, Admin, Admin::RegionsHelper, ApplicationHelper, DeviseHelper, ApplicationController, Admin::ResourceHelper, Admin::ResourceController, Admin::LayoutsHelper, Admin::LayoutsController, MultiSite::SiteChooserHelper, Admin::SnippetsController, ActionText::ContentHelper, and ActionText::TagHelper.
-
-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 TrustyCms::Config, for example,
-the expected changes won't be reflected in that stale Class 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/donavin/Documents/development/trusty-cms/spec/dummy/config/environment.rb:5)
-DEPRECATION WARNING: Initialization autoloaded the constants TrustyCms::Config, Admin, Admin::RegionsHelper, ApplicationHelper, DeviseHelper, ApplicationController, Admin::ResourceHelper, Admin::ResourceController, Admin::LayoutsHelper, Admin::LayoutsController, MultiSite::SiteChooserHelper, Admin::SnippetsController, ActionText::ContentHelper, and ActionText::TagHelper.
-
-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 TrustyCms::Config, for example,
-the expected changes won't be reflected in that stale Class 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/donavin/Documents/development/trusty-cms/spec/dummy/config/environment.rb:5)
-DEPRECATION WARNING: Initialization autoloaded the constants TrustyCms::Config, Admin, Admin::RegionsHelper, ApplicationHelper, DeviseHelper, ApplicationController, Admin::ResourceHelper, Admin::ResourceController, Admin::LayoutsHelper, Admin::LayoutsController, MultiSite::SiteChooserHelper, Admin::SnippetsController, ActionText::ContentHelper, and ActionText::TagHelper.
-
-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 TrustyCms::Config, for example,
-the expected changes won't be reflected in that stale Class 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/donavin/Documents/development/trusty-cms/spec/dummy/config/environment.rb:5)
-DEPRECATION WARNING: Initialization autoloaded the constants TrustyCms::Config, Admin, Admin::RegionsHelper, ApplicationHelper, DeviseHelper, ApplicationController, Admin::ResourceHelper, Admin::ResourceController, Admin::LayoutsHelper, Admin::LayoutsController, MultiSite::SiteChooserHelper, Admin::SnippetsController, ActionText::ContentHelper, and ActionText::TagHelper.
-
-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 TrustyCms::Config, for example,
-the expected changes won't be reflected in that stale Class 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/donavin/Documents/development/trusty-cms/spec/dummy/config/environment.rb:5)
-DEPRECATION WARNING: Initialization autoloaded the constants TrustyCms::Config, Admin, Admin::RegionsHelper, ApplicationHelper, DeviseHelper, ApplicationController, Admin::ResourceHelper, Admin::ResourceController, Admin::LayoutsHelper, Admin::LayoutsController, MultiSite::SiteChooserHelper, Admin::SnippetsController, ActionText::ContentHelper, and ActionText::TagHelper.
-
-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 TrustyCms::Config, for example,
-the expected changes won't be reflected in that stale Class 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/donavin/Documents/development/trusty-cms/spec/dummy/config/environment.rb:5)
-DEPRECATION WARNING: Initialization autoloaded the constants TrustyCms::Config, Admin, Admin::RegionsHelper, ApplicationHelper, DeviseHelper, ApplicationController, Admin::ResourceHelper, Admin::ResourceController, Admin::LayoutsHelper, Admin::LayoutsController, MultiSite::SiteChooserHelper, Admin::SnippetsController, ActionText::ContentHelper, and ActionText::TagHelper.
-
-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 TrustyCms::Config, for example,
-the expected changes won't be reflected in that stale Class 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/donavin/Documents/development/trusty-cms/spec/dummy/config/environment.rb:5)
-DEPRECATION WARNING: Initialization autoloaded the constants TrustyCms::Config, Admin, Admin::RegionsHelper, ApplicationHelper, DeviseHelper, ApplicationController, Admin::ResourceHelper, Admin::ResourceController, Admin::LayoutsHelper, Admin::LayoutsController, MultiSite::SiteChooserHelper, Admin::SnippetsController, ActionText::ContentHelper, and ActionText::TagHelper.
-
-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 TrustyCms::Config, for example,
-the expected changes won't be reflected in that stale Class 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/donavin/Documents/development/trusty-cms/spec/dummy/config/environment.rb:5)
-DEPRECATION WARNING: Initialization autoloaded the constants TrustyCms::Config, Admin, Admin::RegionsHelper, ApplicationHelper, DeviseHelper, ApplicationController, Admin::ResourceHelper, Admin::ResourceController, Admin::LayoutsHelper, Admin::LayoutsController, MultiSite::SiteChooserHelper, Admin::SnippetsController, ActionText::ContentHelper, and ActionText::TagHelper.
-
-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 TrustyCms::Config, for example,
-the expected changes won't be reflected in that stale Class 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/donavin/Documents/development/trusty-cms/spec/dummy/config/environment.rb:5)
-DEPRECATION WARNING: Initialization autoloaded the constants TrustyCms::Config, Admin, Admin::RegionsHelper, ApplicationHelper, DeviseHelper, ApplicationController, Admin::ResourceHelper, Admin::ResourceController, Admin::LayoutsHelper, Admin::LayoutsController, MultiSite::SiteChooserHelper, Admin::SnippetsController, ActionText::ContentHelper, and ActionText::TagHelper.
-
-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 TrustyCms::Config, for example,
-the expected changes won't be reflected in that stale Class 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/donavin/Documents/development/trusty-cms/spec/dummy/config/environment.rb:5)
-DEPRECATION WARNING: Initialization autoloaded the constants TrustyCms::Config, Admin, Admin::RegionsHelper, ApplicationHelper, DeviseHelper, ApplicationController, Admin::ResourceHelper, Admin::ResourceController, Admin::LayoutsHelper, Admin::LayoutsController, MultiSite::SiteChooserHelper, Admin::SnippetsController, ActionText::ContentHelper, and ActionText::TagHelper.
-
-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 TrustyCms::Config, for example,
-the expected changes won't be reflected in that stale Class 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/donavin/Documents/development/trusty-cms/spec/dummy/config/environment.rb:5)