super_settings 1.0.1 → 2.0.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: f58b7aa08a4a6082168ff9fa1487f79ff84bf9374b9463d9ba3ebe4e188b6a47
-  data.tar.gz: b4bf73f87885acacc091e3f455a8a33a8b0baa770dd00db42a1fac6b468e5427
+  metadata.gz: 83d20aa4f55a73597f12a1fed76db8d01bd81ec128b5208ed60ff8acc82a273b
+  data.tar.gz: c2bf00fe10c179d9ddc6849fbc6b2be2eb511b8132463a143e202ea42996581b
 SHA512:
-  metadata.gz: 973a1ac38488a2cdc4d4cc639f9057d8a1cfd24e216cd7b8cfe4b034af5085b3e0245999b918f3aac7a95416d47fcba46f099d8312afaa2406f63bd5a17f1d25
-  data.tar.gz: e1922327a1c8965dd72d8b11826f398b7dd0cd4f3a3f27be7cc3aa5a81f44da925a159ae2321a122267a9605dd7fbb5fa6af909d4daeeae3cf371087b4df7a7f
+  metadata.gz: 6fec2ccebbc1f84a7bb1878c4b6ea5f9fb5b36eacb0fddc3fcc2520ce3e738d895bf540be762a225aab970cc102287f5598b99588f4ad82494b726306b3f4601
+  data.tar.gz: 4d9d0641b7b47a845c26f6e72fccdd996c81b5e5f25c88d93b9148ca1c1767fe4c4d97681b558af0490028cbac3ac9e1ac447271b971829f2e8f3ea2a11311fd

data/CHANGELOG.md

@@ -4,12 +4,44 @@ All notable changes to this project will be documented in this file.
 The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
 and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
 
-## [1.0.1]
+## 2.0.0
+
+### Added
+
+- Added controls for sorting settings in the web UI by keys or last modified time.
+- Isolated of CSS classes in the web UI to prevent conflicts with other CSS libraries.
+- Dark mode support in web UI.
+- Added ability to embed the web UI in a view to allow tighter integration with your application's UI.
+- Added storage adapter for storing settings in an S3 object.
+- Added storage adapter for storing settings in MongoDB.
+- HTTP storage adapter now uses keep-alive connections to improve performance.
+
+### Fixed
+
+- Changing a key now works as expected. Previously, a new setting was created with the new key and the old setting was left unchanged. Now, the old setting is properly marked as deleted.
+- Consistently handle converting floating point number to timestamps in Redis storage.
+
+### Removed
+
+- Rails 4.2, 5.0, and 5.1 support has been removed.
+- Removed support for Ruby 2.5.
+
+## 1.0.2
+
+### Added
+
+- Added SuperSetting.rand method that can return a consistent random number inside of a context block.
+
+### Changed
+
+- Lazy load non-required classes.
+
+## 1.0.1
 
 ### Added
 - Optimize object shapes for the Ruby interpreter by declaring instance variables in constructors.
 
-## [1.0.0]
+## 1.0.0
 
 ### Added
 - Everything!

data/README.md

@@ -1,28 +1,28 @@
 # SuperSettings
 
 [![Continuous Integration](https://github.com/bdurand/super_settings/actions/workflows/continuous_integration.yml/badge.svg)](https://github.com/bdurand/super_settings/actions/workflows/continuous_integration.yml)
-[![Regression Test](https://github.com/bdurand/super_settings/actions/workflows/regression_test.yml/badge.svg)](https://github.com/bdurand/super_settings/actions/workflows/regression_test.yml)
 [![Ruby Style Guide](https://img.shields.io/badge/code_style-standard-brightgreen.svg)](https://github.com/testdouble/standard)
+[![Gem Version](https://badge.fury.io/rb/super_settings.svg)](https://badge.fury.io/rb/super_settings)
 
-This gem provides a framework for maintaining runtime application settings. Settings are persisted in a database but cached in memory for quick, efficient access. The settings are designed so they can be updated dynamically without requiring code deployment or restarting processes. The code scales very well and can easily handle very high throughput environments.
+SuperSettings is a Ruby gem that provides a scalable framework for maintaining runtime application settings. Settings are persisted in a database but cached in memory for quick, efficient access. This design ensures settings can be updated dynamically without requiring code deployment or process restarts, making it ideal for high-throughput environments.
 
-As applications grow, they tend to accumulate many configuration options. Often these end up in environment variables, hard coded in YAML files, or sprinkled through various data models as additional columns. All of these methods of configuration have their place and are completely appropriate for different purposes (i.e. for storing application secrets, configuration required during application startup, etc.).
+As applications grow, they often accumulate a large number of configuration options. Common approaches such as environment variables, YAML files, or additional database columns all have their place:
 
-However, these methods don't work as well for runtime settings that you may want to change while your application is running.
+- **Environment variables** are suitable for environment-specific configuration, but require restarts for changes to take effect and can only store string values.
+- **YAML files** offer support for complex data structures and can be bundled with application code but typically require a new release to update.
+- **Database columns** - These are great for settings tied to data models; however, they don’t apply well outside of the data model, and you need to build custom tools to manage them in your application.
 
-- **Environment variables** - These are great for environment-specific configuration and they can be a good place to store sensitive data. However, they can be difficult to manage. All values must be stored as strings, and application processes need to be restarted for changes to take effect.
+Key features include:
 
-- **YAML files** - These are great for more complex configurations because they support data structures and they can be shipped with your application code. However, changing them usually requires a new release of the application.
+- **Caching:** A thread-safe, in-memory caching mechanism ensures high-performance access to settings, while minimizing database load. Cache refreshes are highly efficient and configurable.
+- **Dynamic Updates:** Settings can be changed on the fly, with automatic logging of changes to maintain an audit trail for compliance.
+- **Data Types and Validation:** Settings can be defined with specific data types (string, integer, float, boolean, datetime, or array) to ensure validity.
+- **Documentation:** Each setting can include a description to explain its purpose and usage.
+- **Web UI and REST API:** Manage settings via a built-in web interface or REST API.
+- **Custom Callbacks:** Execute custom logic whenever a setting changes, enabling more sophisticated behavior for logging and compliance.
+- **Pluggable Data Storage:** SuperSettings supports multiple storage engines, including ActiveRecord, Redis, and S3. You can also chain it to another application running SuperSettings via the HTTP storage engine to allow microservices to share settings.
 
-- **Database columns** - These are great for settings tied to data models, however, they don't apply very well outside the data model, and you need to build the tools for managing them into your application.
-
-SuperSettings provides a simple interface for accessing settings backed by a thread-safe caching mechanism, which provides in-memory performance while significantly limiting any load on the database. You can tune how frequently the cache is refreshed and each refresh call is tuned to be highly efficient.
-
-There is also an out of the box Web UI and REST API for managing settings. You can specify data types for your settings (string, integer, float, boolean, datetime, or array) to ensure that values will be valid. You can also supply documentation for each setting so that it's clear what each one does and how it is used.
-
-Changes to settings are stored whenever a setting is changed to give you an audit trail if you need it for compliance reasons. In addition, you can provide your own callbacks to execute whenever a setting is changed.
-
-There is a companion gem [ultra_settings](https://github.com/bdurand/ultra_settings) that can be used to integrate SuperSettings into a combined configuration system alongside YAML files and environment variables.
+For projects that require a combination of runtime settings, environment variables, and YAML files, SuperSettings integrates seamlessly with [ultra_settings](https://github.com/bdurand/ultra_settings), creating a flexible and powerful configuration system.
 
 ## Usage
 
@@ -102,6 +102,16 @@ SuperSettings.context do
 end
 ```
 
+You can also use the `SuperSettings.rand` method inside a context block to return a consistent random number. This can be useful for things like feature flags that you want to turn on for only a percentage of requests:
+
+```ruby
+def enabled?
+  SuperSettings.float("feature_rollout_percent") <= SuperSettings.rand
+end
+```
+
+Now the value of `enabled?` will always return the same value inside of a context block. It will still be random if it is enabled for each context block.
+
 It's a good idea to add a `context` block around your main unit of work:
 
 - Rack application: add `SuperSettings::Context::RackMiddleware` to your middleware stack
@@ -137,10 +147,11 @@ This gem abstracts out the storage engine and can support multiple storage mecha
 * `SuperSettings::Storage::ActiveRecordStorage` - Stores the settings in a relational database using ActiveRecord. This is the default storage engine for Rails applications.
 * `SuperSettings::Storage::RedisStorage` - Stores the settings in a Redis database using the [redis](https://github.com/redis/redis-rb) gem.
 * `SuperSettings::Storage::HttpStorage` - Uses the SuperSettings REST API running on another server. This is useful in a microservices architecture so you can have a central settings server used by all the services.
+* `SuperSettings::Storage::S3Storage` - Stores the settings in JSON in an S3 object. This is useful for applications running on AWS that want to store settings in a central location since it does not require a dedicated database. It is possible to read the settings directly from S3 from another application.
 
 Additional storage engines can be built by creating a class that includes `SuperSettings::Storage` and implements the unimplemented methods in that module.
 
-The storage engine is defined by setting `SuperSettings::Setting.storage` to a storage class. Note that each storage class may also require additional configuration. For instance, the Redis storage class requires you to provide a connection to a Redis database. If you are running a Rails application, then the storage engine will be set to ActiveRecord by default. Otherwise, you will need to define the storage class somewhere in your application's initialization.
+The storage engine is defined by setting `SuperSettings::Setting.storage` to a storage class. Note that each storage class may also require additional configuration. For instance, the Redis storage class requires you to provide a connection to a Redis database. If you are running a Rails application, then the storage engine will be set to ActiveRecord by default. Otherwise, you will need to define the storage class somewhere in your application's initialization. See the storage class documentation for more information.
 
 ### Web UI
 
@@ -231,6 +242,9 @@ SuperSettings.configure do |config|
   # Set the superclass to use for the controller. Defaults to using `ApplicationController`.
   config.controller.superclass = Admin::BaseController
 
+  # Set the color scheme to use for the Web UI. Options are :light (default), :dark, or :system.
+  config.controller.color_scheme = :dark
+
   # Add additional code to the controller. In this case we are adding code to ensure only
   # admins can access the functionality and changing the layout to use one defined by the application.
   config.controller.enhance do
@@ -278,6 +292,54 @@ SuperSettings.configure do |config|
 end
 ```
 
+#### Using your own controller
+
+You can embed the SuperSettings web UI into your own templates. This gives you the option to more tightly integrate it with your application's navigation and look and feel.
+
+First disable the web UI in the configuration since you won't need it.
+
+```ruby
+# config/initializers/super_settings.rb
+
+SuperSettings.configure do |config|
+  # Disable the built in web UI since you won't be using it.
+  config.controller.web_ui_enabled = false
+end
+```
+
+Create your controller that will render the SuperSettings web UI.
+
+```ruby
+class AppSettingsController < ApplicationController
+  def index
+  end
+end
+```
+
+Mount the engine routes in your `config/routes.rb` file.
+
+```ruby
+# config/routes.rb
+
+Rails.application.routes.draw do
+  mount SuperSettings::Engine => "/settings"
+
+  controller :app_settings do
+    get "/app_settings", action: :index
+  end
+end
+```
+
+Create a view that embeds the SuperSettings web UI using the `SuperSettings::Application` class. You need to specify the path you mounted the engine at as the base URL for the REST API.
+
+```erb
+# app/views/app_settings/index.html.erb
+
+<h1>Application Settings</h1>
+
+<%= SuperSettings::Application.new(api_base_url: "/settings").render %>
+```
+
 ## Installation
 
 Add this line to your application's Gemfile:
@@ -302,6 +364,49 @@ Open a pull request on GitHub.
 
 Please use the [standardrb](https://github.com/testdouble/standard) syntax and lint your code with `standardrb --fix` before submitting.
 
+You can run a local Rails development using ActiveRecord storage with
+
+```bash
+# Initialize the database (one time only)
+bin/rails bin/rails super_settings:install:migrations
+bin/rails db:migrate
+
+# Start the server
+bin/rails s
+```
+
+You can also bring up a local rack server with
+
+```bash
+bundle exec rackup
+```
+
+By default this will use Redis for storage using the default Redis URL. You can change the storage engine with the `STORAGE` environment variable.
+
+- `redis` - Use the Redis storage engine. The Redis URL can be set with the `REDIS_URL` environment variable.
+- `http` - Use the HTTP storage engine. The URL for the REST API can be set with the `REST_API_URL` environment variable.
+- `s3` - Use the S3 storage engine. The S3 URL can be set with the `S3_URL` environment variable.
+- `mongodb` - Use the MongoDB storage engine. The MongoDB URL can be set with the `MONGODB_URL` environment variable.
+
+You can bring up all of these storage engines locally with the included docker-compose configuration.
+
+```bash
+docker-compose up
+```
+
+This will work out of the box with the defaults for the storage engines when running the rack server.:
+
+- `REDIS_URL` - `redis://localhost:6379/0`
+- `REST_API_URL` - `http://localhost:3000/settings` (this is the default URL for the Rails application)
+- `S3_URL` - `s3://accesskey:secretkey@region-1/settings/settings.json` (the S3 endpoint will be set to `http://localhost:9000`)
+- `MONGODB_URL` - `mongodb://localhost:27017/super_settings`
+
+Finally, you can run the application in dark mode by setting the `COLOR_SCHEME` environment variable.
+
+```bash
+COLOR_SCHEME=dark bundle exec rackup
+```
+
 ## License
 
 The gem is available as open source under the terms of the [MIT License](https://opensource.org/licenses/MIT).

data/VERSION

@@ -1 +1 @@
-1.0.1
+2.0.0

data/app/helpers/super_settings/settings_helper.rb

@@ -5,19 +5,20 @@ module SuperSettings
     # Render the styles.css as an inline <style> tag.
     def super_settings_layout_style_tag
       application_dir = File.expand_path(File.join("..", "..", "..", "lib", "super_settings", "application"), __dir__)
+      css = render(file: File.join(application_dir, "layout_styles.css"))
       content_tag(:style, type: "text/css") do
-        render(file: File.join(application_dir, "layout_styles.css")).html_safe
+        (layout_css_vars + css).html_safe
       end
     end
 
     # Return the application name set by the configuration or a default value.
     def super_settings_application_name
-      Configuration.instance.controller.application_name || "Application"
+      SuperSettings.configuration.controller.application_name || "Application"
     end
 
     # Render the header for the web pages using values set in the configuration.
     def super_settings_application_header
-      config = Configuration.instance.controller
+      config = SuperSettings.configuration.controller
       content = "#{super_settings_application_name} Settings"
       if Coerce.present?(config.application_logo)
         content = image_tag(config.application_logo, alt: "").concat(content)
@@ -28,5 +29,14 @@ module SuperSettings
         content
       end
     end
+
+    private
+
+    def layout_css_vars
+      application_dir = File.expand_path(File.join("..", "..", "..", "lib", "super_settings", "application"), __dir__)
+      erb = ERB.new(File.read(File.join(application_dir, "layout_vars.css.erb")))
+      color_scheme = SuperSettings.configuration.controller.color_scheme
+      erb.result(binding).html_safe
+    end
   end
 end

data/app/views/layouts/super_settings/settings.html.erb

@@ -13,7 +13,7 @@
         <%= super_settings_application_header %>
       </h1>
     </header>
-    <div class="container">
+    <div class="super-settings-container">
       <%= yield %>
     </div>
   </body>

data/config/routes.rb

@@ -2,7 +2,7 @@
 
 SuperSettings::Engine.routes.draw do
   controller :settings do
-    if SuperSettings::Configuration.instance.controller.web_ui_enabled?
+    if SuperSettings.configuration.controller.web_ui_enabled?
       get "/", action: :root, as: :root
     end
     get "/settings", action: :index

data/db/migrate/20210414004553_create_super_settings.rb

@@ -1,12 +1,6 @@
 # frozen_string_literal: true
 
-# Needed for the super_settings gem to maintain backward compatibility with Rails 4.2
-migration_class = ActiveRecord::Migration
-if migration_class.respond_to?(:[])
-  migration_class = migration_class[4.2]
-end
-
-class CreateSuperSettings < migration_class
+class CreateSuperSettings < ActiveRecord::Migration[5.0]
   def up
     create_table :super_settings do |t|
       t.string :key, null: false, limit: 190, index: {unique: true}

data/lib/super_settings/application/api.js

@@ -9,7 +9,10 @@
 (function() {
   // Get the URL for making an API call to the specified action and id.
   function apiURL(action, params) {
-    let url = window.location.pathname;
+    let url = document.querySelector(".super-settings[data-api-base-url]")?.dataset?.apiBaseUrl;
+    if (!url) {
+      url = window.location.pathname;
+    }
     if (url.endsWith("/")) {
       url = url.substring(0, url.length - 1);
     }

data/lib/super_settings/application/helper.rb

@@ -5,13 +5,14 @@ module SuperSettings
   # are mixed in to the Application class so they are accessible from the ERB templates.
   module Helper
     ICON_SVG = Dir.glob(File.join(__dir__, "images", "*.svg")).each_with_object({}) do |file, cache|
-      cache[File.basename(file, ".svg")] = File.read(file).chomp
+      svg = File.read(file).chomp
+      cache[File.basename(file, ".svg")] = svg
     end.freeze
 
     ICON_BUTTON_STYLE = {
       cursor: "pointer",
-      width: "1.5rem",
-      height: "1.5rem",
+      width: "1.35rem",
+      height: "1.35rem",
       "min-width": "20px",
       "min-height": "20px",
       "margin-top": "0.25rem",
@@ -21,8 +22,7 @@ module SuperSettings
     DEFAULT_ICON_STYLE = {
       width: "1rem",
       height: "1rem",
-      display: "inline-block",
-      "vertical-align": "middle"
+      display: "inline-block"
     }.freeze
 
     # Render the scripts.js file as an inline <script> tag.
@@ -41,6 +41,7 @@ module SuperSettings
     def style_tag
       <<~HTML
         <style type="text/css">
+          #{render_partial("style_vars.css.erb")}
           #{File.read(File.join(__dir__, "styles.css"))}
         </style>
       HTML
@@ -50,39 +51,61 @@ module SuperSettings
     def layout_style_tag
       <<~HTML
         <style type="text/css">
+          #{render_partial("layout_vars.css.erb")}
           #{File.read(File.join(__dir__, "layout_styles.css"))}
         </style>
       HTML
     end
 
+    # Render an ERB template.
+    #
+    # @param erb_file [String] the path to the ERB file to render
+    # @return [String] the rendered HTML
+    def render_partial(erb_file)
+      template = ERB.new(File.read(File.expand_path(erb_file, __dir__)))
+      template.result(binding)
+    end
+
+    # Escape text for use in HTML.
+    #
+    # @param text [String] the text to escape
+    # @return [String] the escaped text
+    def html_escape(text)
+      ERB::Util.html_escape(text)
+    end
+
     # Render an image tag for one of the SVG images in the images directory. If the :color option
     # is specified, it will be applied to the SVG image.
     def icon_image(name, options = {})
       svg = ICON_SVG[name.to_s]
-      if Coerce.present?(options[:color])
-        svg = svg.gsub("currentColor", options[:color])
+      style = (options[:style] || {})
+      css = DEFAULT_ICON_STYLE.merge(style).map { |name, value| "#{name}: #{value}" }.join("; ")
+      options = options.merge(style: css, class: "super-settings-icon")
+      if options[:data].is_a?(Hash)
+        options[:data].each do |key, value|
+          options["data-#{key}"] = value
+        end
+        options.delete(:data)
       end
-      css = DEFAULT_ICON_STYLE.merge(options[:style] || {}).map { |name, value| "#{name}:#{value}" }.join("; ")
-      options = {alt: ""}.merge(options).merge(src: "data:image/svg+xml;utf8,#{svg}", style: css)
-      tag(:img, options)
+      content_tag(:span, svg, options)
     end
 
     # Render an icon image as a link tag.
     def icon_button(icon, title:, color:, js_class:, url: nil, disabled: false, style: {}, link_style: nil)
       url = "#" if Coerce.blank?(url)
-      image = icon_image(icon, alt: title, color: color, style: ICON_BUTTON_STYLE.merge(style))
-      content_tag(:a, image, href: url, class: js_class, disabled: disabled, style: link_style)
+      image = icon_image(icon, alt: title, style: ICON_BUTTON_STYLE.merge(style).merge(color: color))
+      content_tag(:a, image, href: url, class: js_class, disabled: disabled, style: link_style, title: title)
     end
 
     # Return the application name set by the configuration or a default value.
     def application_name
-      ERB::Util.html_escape(Configuration.instance.controller.application_name || "Application")
+      html_escape(SuperSettings.configuration.controller.application_name || "Application")
     end
 
     # Render the header for the web pages using values set in the configuration.
     def application_header
-      config = Configuration.instance.controller
-      content = ERB::Util.html_escape("#{application_name} Settings")
+      config = SuperSettings.configuration.controller
+      content = html_escape("#{application_name} Settings")
       if Coerce.present?(config.application_logo)
         content = tag(:img, src: config.application_logo, alt: "") + content
       end
@@ -107,14 +130,30 @@ module SuperSettings
     def html_attributes(options)
       html_options = []
       options.each do |name, value|
-        html_options << "#{name}=\"#{ERB::Util.html_escape(value.to_s)}\""
+        html_options << "#{name}=\"#{html_escape(value.to_s)}\""
       end
       html_options.join(" ")
     end
 
-    # Add additional HTML code to the <head> element on the page.
+    # Additional HTML code that should go into the <head> element on the page.
+    #
+    # @return [String]
     def add_to_head
       @add_to_head if defined?(@add_to_head)
     end
+
+    # The base URL for the REST API.
+    #
+    # @return [String]
+    def api_base_url
+      @api_base_url if defined?(@api_base_url)
+    end
+
+    # Whether to use dark mode for the application UI.
+    #
+    # @return [Boolean, nil]
+    def color_scheme
+      @color_scheme if defined?(@color_scheme)
+    end
   end
 end

data/lib/super_settings/application/images/arrow-down-short.svg

@@ -0,0 +1,3 @@
+<svg xmlns="http://www.w3.org/2000/svg" width="16" height="16" fill="currentColor" class="bi bi-arrow-down-short" viewBox="0 0 16 16">
+  <path fill-rule="evenodd" d="M8 4a.5.5 0 0 1 .5.5v5.793l2.146-2.147a.5.5 0 0 1 .708.708l-3 3a.5.5 0 0 1-.708 0l-3-3a.5.5 0 1 1 .708-.708L7.5 10.293V4.5A.5.5 0 0 1 8 4"/>
+</svg>

data/lib/super_settings/application/images/arrow-up-short.svg

@@ -0,0 +1,3 @@
+<svg xmlns="http://www.w3.org/2000/svg" width="16" height="16" fill="currentColor" class="bi bi-arrow-up-short" viewBox="0 0 16 16">
+  <path fill-rule="evenodd" d="M8 12a.5.5 0 0 0 .5-.5V5.707l2.146 2.147a.5.5 0 0 0 .708-.708l-3-3a.5.5 0 0 0-.708 0l-3 3a.5.5 0 1 0 .708.708L7.5 5.707V11.5a.5.5 0 0 0 .5.5"/>
+</svg>

data/lib/super_settings/application/images/info-circle.svg

@@ -0,0 +1,4 @@
+<svg xmlns="http://www.w3.org/2000/svg" width="16" height="16" fill="currentColor" class="bi bi-info-circle" viewBox="0 0 16 16">
+  <path d="M8 15A7 7 0 1 1 8 1a7 7 0 0 1 0 14m0 1A8 8 0 1 0 8 0a8 8 0 0 0 0 16"/>
+  <path d="m8.93 6.588-2.29.287-.082.38.45.083c.294.07.352.176.288.469l-.738 3.468c-.194.897.105 1.319.808 1.319.545 0 1.178-.252 1.465-.598l.088-.416c-.2.176-.492.246-.686.246-.275 0-.375-.193-.304-.533zM9 4.5a1 1 0 1 1-2 0 1 1 0 0 1 2 0"/>
+</svg>

data/lib/super_settings/application/images/pencil-square.svg

@@ -0,0 +1,4 @@
+<svg xmlns="http://www.w3.org/2000/svg" width="16" height="16" fill="currentColor" class="bi bi-pencil-square" viewBox="0 0 16 16">
+  <path d="M15.502 1.94a.5.5 0 0 1 0 .706L14.459 3.69l-2-2L13.502.646a.5.5 0 0 1 .707 0l1.293 1.293zm-1.75 2.456-2-2L4.939 9.21a.5.5 0 0 0-.121.196l-.805 2.414a.25.25 0 0 0 .316.316l2.414-.805a.5.5 0 0 0 .196-.12l6.813-6.814z"/>
+  <path fill-rule="evenodd" d="M1 13.5A1.5 1.5 0 0 0 2.5 15h11a1.5 1.5 0 0 0 1.5-1.5v-6a.5.5 0 0 0-1 0v6a.5.5 0 0 1-.5.5h-11a.5.5 0 0 1-.5-.5v-11a.5.5 0 0 1 .5-.5H9a.5.5 0 0 0 0-1H2.5A1.5 1.5 0 0 0 1 2.5z"/>
+</svg>

data/lib/super_settings/application/images/plus.svg

@@ -1 +1,3 @@
-<svg xmlns="http://www.w3.org/2000/svg" width="24" height="24" viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round" stroke-linejoin="round" class="feather feather-plus"><line x1="12" y1="5" x2="12" y2="19"></line><line x1="5" y1="12" x2="19" y2="12"></line></svg>
+<svg xmlns="http://www.w3.org/2000/svg" width="16" height="16" fill="currentColor" class="bi bi-plus" viewBox="0 0 16 16">
+  <path d="M8 4a.5.5 0 0 1 .5.5v3h3a.5.5 0 0 1 0 1h-3v3a.5.5 0 0 1-1 0v-3h-3a.5.5 0 0 1 0-1h3v-3A.5.5 0 0 1 8 4"/>
+</svg>

data/lib/super_settings/application/images/trash3.svg

@@ -0,0 +1,3 @@
+<svg xmlns="http://www.w3.org/2000/svg" width="16" height="16" fill="currentColor" class="bi bi-trash3" viewBox="0 0 16 16">
+  <path d="M6.5 1h3a.5.5 0 0 1 .5.5v1H6v-1a.5.5 0 0 1 .5-.5M11 2.5v-1A1.5 1.5 0 0 0 9.5 0h-3A1.5 1.5 0 0 0 5 1.5v1H1.5a.5.5 0 0 0 0 1h.538l.853 10.66A2 2 0 0 0 4.885 16h6.23a2 2 0 0 0 1.994-1.84l.853-10.66h.538a.5.5 0 0 0 0-1zm1.958 1-.846 10.58a1 1 0 0 1-.997.92h-6.23a1 1 0 0 1-.997-.92L3.042 3.5zm-7.487 1a.5.5 0 0 1 .528.47l.5 8.5a.5.5 0 0 1-.998.06L5 5.03a.5.5 0 0 1 .47-.53Zm5.058 0a.5.5 0 0 1 .47.53l-.5 8.5a.5.5 0 1 1-.998-.06l.5-8.5a.5.5 0 0 1 .528-.47M8 4.5a.5.5 0 0 1 .5.5v8.5a.5.5 0 0 1-1 0V5a.5.5 0 0 1 .5-.5"/>
+</svg>

data/lib/super_settings/application/images/x-circle.svg

@@ -0,0 +1,4 @@
+<svg xmlns="http://www.w3.org/2000/svg" width="16" height="16" fill="currentColor" class="bi bi-x-circle" viewBox="0 0 16 16">
+  <path d="M8 15A7 7 0 1 1 8 1a7 7 0 0 1 0 14m0 1A8 8 0 1 0 8 0a8 8 0 0 0 0 16"/>
+  <path d="M4.646 4.646a.5.5 0 0 1 .708 0L8 7.293l2.646-2.647a.5.5 0 0 1 .708.708L8.707 8l2.647 2.646a.5.5 0 0 1-.708.708L8 8.707l-2.646 2.647a.5.5 0 0 1-.708-.708L7.293 8 4.646 5.354a.5.5 0 0 1 0-.708"/>
+</svg>