apidae 1.4.21 → 2.0.0

data/test/dummy/log/development.log

@@ -13845,401 +13845,3 @@ Migrating to MigrateLocalizedApidaeObjFields (20190127210921)
   Apidae::Obj Load (2.4ms)  SELECT "apidae_objs".* FROM "apidae_objs" WHERE "apidae_objs"."root_obj_id" IS NULL
   TRANSACTION (0.8ms)  ROLLBACK
    (0.5ms)  SELECT pg_advisory_unlock(6140174353533887940)
-   (0.1ms)  SELECT pg_try_advisory_lock(6140174353533887940)
-  ActiveRecord::SchemaMigration Load (1.9ms)  SELECT "schema_migrations"."version" FROM "schema_migrations" ORDER BY "schema_migrations"."version" ASC
-  ActiveRecord::InternalMetadata Load (2.2ms)  SELECT * FROM "ar_internal_metadata" WHERE "ar_internal_metadata"."key" = $1 ORDER BY "ar_internal_metadata"."key" ASC LIMIT 1  [[nil, "environment"]]
-Migrating to MigrateLocalizedApidaeReferences (20190127213602)
-  TRANSACTION (0.2ms)  BEGIN
-  TRANSACTION (0.1ms)  ROLLBACK
-   (0.3ms)  SELECT pg_advisory_unlock(6140174353533887940)
-   (2.0ms)  SELECT pg_try_advisory_lock(6140174353533887940)
-  ActiveRecord::SchemaMigration Load (1.8ms)  SELECT "schema_migrations"."version" FROM "schema_migrations" ORDER BY "schema_migrations"."version" ASC
-  ActiveRecord::InternalMetadata Load (2.6ms)  SELECT * FROM "ar_internal_metadata" WHERE "ar_internal_metadata"."key" = $1 ORDER BY "ar_internal_metadata"."key" ASC LIMIT 1  [[nil, "environment"]]
-Migrating to MigrateLocalizedApidaeReferences (20190127213602)
-  TRANSACTION (0.6ms)  BEGIN
-  TRANSACTION (0.6ms)  ROLLBACK
-   (0.4ms)  SELECT pg_advisory_unlock(6140174353533887940)
-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)
-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)
-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)

data/test/dummy/public/404.html

@@ -4,7 +4,7 @@
   <title>The page you were looking for doesn't exist (404)</title>
   <meta name="viewport" content="width=device-width,initial-scale=1">
   <style>
-  body {
+  .rails-default-error-page {
     background-color: #EFEFEF;
     color: #2E2F30;
     text-align: center;
@@ -12,13 +12,13 @@
     margin: 0;
   }
 
-  div.dialog {
+  .rails-default-error-page div.dialog {
     width: 95%;
     max-width: 33em;
     margin: 4em auto 0;
   }
 
-  div.dialog > div {
+  .rails-default-error-page div.dialog > div {
     border: 1px solid #CCC;
     border-right-color: #999;
     border-left-color: #999;
@@ -31,13 +31,13 @@
     box-shadow: 0 3px 8px rgba(50, 50, 50, 0.17);
   }
 
-  h1 {
+  .rails-default-error-page h1 {
     font-size: 100%;
     color: #730E15;
     line-height: 1.5em;
   }
 
-  div.dialog > p {
+  .rails-default-error-page div.dialog > p {
     margin: 0 0 1em;
     padding: 1em;
     background-color: #F7F7F7;
@@ -54,7 +54,7 @@
   </style>
 </head>
 
-<body>
+<body class="rails-default-error-page">
   <!-- This file lives in public/404.html -->
   <div class="dialog">
     <div>

data/test/dummy/public/406-unsupported-browser.html

@@ -0,0 +1,66 @@
+<!DOCTYPE html>
+<html>
+<head>
+  <title>Your browser is not supported (406)</title>
+  <meta name="viewport" content="width=device-width,initial-scale=1">
+  <style>
+  .rails-default-error-page {
+    background-color: #EFEFEF;
+    color: #2E2F30;
+    text-align: center;
+    font-family: arial, sans-serif;
+    margin: 0;
+  }
+
+  .rails-default-error-page div.dialog {
+    width: 95%;
+    max-width: 33em;
+    margin: 4em auto 0;
+  }
+
+  .rails-default-error-page div.dialog > div {
+    border: 1px solid #CCC;
+    border-right-color: #999;
+    border-left-color: #999;
+    border-bottom-color: #BBB;
+    border-top: #B00100 solid 4px;
+    border-top-left-radius: 9px;
+    border-top-right-radius: 9px;
+    background-color: white;
+    padding: 7px 12% 0;
+    box-shadow: 0 3px 8px rgba(50, 50, 50, 0.17);
+  }
+
+  .rails-default-error-page h1 {
+    font-size: 100%;
+    color: #730E15;
+    line-height: 1.5em;
+  }
+
+  .rails-default-error-page div.dialog > p {
+    margin: 0 0 1em;
+    padding: 1em;
+    background-color: #F7F7F7;
+    border: 1px solid #CCC;
+    border-right-color: #999;
+    border-left-color: #999;
+    border-bottom-color: #999;
+    border-bottom-left-radius: 4px;
+    border-bottom-right-radius: 4px;
+    border-top-color: #DADADA;
+    color: #666;
+    box-shadow: 0 3px 8px rgba(50, 50, 50, 0.17);
+  }
+  </style>
+</head>
+
+<body class="rails-default-error-page">
+  <!-- This file lives in public/406-unsupported-browser.html -->
+  <div class="dialog">
+    <div>
+      <h1>Your browser is not supported.</h1>
+      <p>Please upgrade your browser to continue.</p>
+    </div>
+  </div>
+</body>
+</html>

data/test/dummy/public/422.html

@@ -4,7 +4,7 @@
   <title>The change you wanted was rejected (422)</title>
   <meta name="viewport" content="width=device-width,initial-scale=1">
   <style>
-  body {
+  .rails-default-error-page {
     background-color: #EFEFEF;
     color: #2E2F30;
     text-align: center;
@@ -12,13 +12,13 @@
     margin: 0;
   }
 
-  div.dialog {
+  .rails-default-error-page div.dialog {
     width: 95%;
     max-width: 33em;
     margin: 4em auto 0;
   }
 
-  div.dialog > div {
+  .rails-default-error-page div.dialog > div {
     border: 1px solid #CCC;
     border-right-color: #999;
     border-left-color: #999;
@@ -31,13 +31,13 @@
     box-shadow: 0 3px 8px rgba(50, 50, 50, 0.17);
   }
 
-  h1 {
+  .rails-default-error-page h1 {
     font-size: 100%;
     color: #730E15;
     line-height: 1.5em;
   }
 
-  div.dialog > p {
+  .rails-default-error-page div.dialog > p {
     margin: 0 0 1em;
     padding: 1em;
     background-color: #F7F7F7;
@@ -54,7 +54,7 @@
   </style>
 </head>
 
-<body>
+<body class="rails-default-error-page">
   <!-- This file lives in public/422.html -->
   <div class="dialog">
     <div>

data/test/dummy/public/500.html

@@ -4,7 +4,7 @@
   <title>We're sorry, but something went wrong (500)</title>
   <meta name="viewport" content="width=device-width,initial-scale=1">
   <style>
-  body {
+  .rails-default-error-page {
     background-color: #EFEFEF;
     color: #2E2F30;
     text-align: center;
@@ -12,13 +12,13 @@
     margin: 0;
   }
 
-  div.dialog {
+  .rails-default-error-page div.dialog {
     width: 95%;
     max-width: 33em;
     margin: 4em auto 0;
   }
 
-  div.dialog > div {
+  .rails-default-error-page div.dialog > div {
     border: 1px solid #CCC;
     border-right-color: #999;
     border-left-color: #999;
@@ -31,13 +31,13 @@
     box-shadow: 0 3px 8px rgba(50, 50, 50, 0.17);
   }
 
-  h1 {
+  .rails-default-error-page h1 {
     font-size: 100%;
     color: #730E15;
     line-height: 1.5em;
   }
 
-  div.dialog > p {
+  .rails-default-error-page div.dialog > p {
     margin: 0 0 1em;
     padding: 1em;
     background-color: #F7F7F7;
@@ -54,7 +54,7 @@
   </style>
 </head>
 
-<body>
+<body class="rails-default-error-page">
   <!-- This file lives in public/500.html -->
   <div class="dialog">
     <div>

data/test/dummy/public/icon.svg

@@ -0,0 +1,3 @@
+<svg width="100" height="100" xmlns="http://www.w3.org/2000/svg">
+  <rect width="100%" height="100%" fill="red"/>
+</svg>

data/test/dummy/public/robots.txt

@@ -0,0 +1 @@
+# See https://www.robotstxt.org/robotstxt.html for documentation on how to use the robots.txt file