configurations.rb

[geekelo]

FILE

ActiveAdmin.register ConfigurationSetting do

  actions :all, except: :destroy

  config.sort_order = 'name'

  menu parent: 'Configuration', label: 'General'

  # See permitted parameters documentation:
  # https://github.com/activeadmin/activeadmin/blob/master/docs/2-resource-customization.md#setting-up-strong-parameters
  #
  # Uncomment all parameters which should be permitted for assignment
  #
  permit_params :name, :slug, :configuration_type, :description, :resource, :active, :data
  #
  # or
  #
  # permit_params do
  #   permitted = [:name, :type, :description, :active, :data]
  #   permitted << :other if params[:action] == 'create' && current_user.admin?
  #   permitted
  # end

  index do
    selectable_column
    id_column
    column :slug
    column :name
    column :configuration_type
    column :description
    column :active
  end
end

[geekelo]

This file sets up the ActiveAdmin interface for managing ConfigurationSetting records, with a focus on allowing all actions except for deletion. The configuration includes menu placement, permitted parameters, and index page customization.

File: configuration_setting.rb

1. Actions Configuration

• actions :all, except: :destroy
  • This line enables all CRUD actions (index, show, new, create, edit, update) except for the destroy action. This restriction could be in place to prevent accidental deletion of important configuration settings.

2. Sorting Configuration

• config.sort_order = 'name'
  • This sets the default sorting order to be by the name attribute. When administrators view the list of configuration settings, they will be sorted alphabetically by name.

3. Menu Configuration

• menu parent: 'Configuration', label: 'General'
  • The ConfigurationSetting resource is placed under the "Configuration" menu with the label "General." This categorizes it appropriately within the admin interface, making it easier to navigate.

4. Permitted Parameters

• permit_params :name, :slug, :configuration_type, :description, :resource, :active, :data
  • This defines the parameters that are allowed for mass assignment. The specified attributes can be set or modified through forms in the ActiveAdmin interface.
  • Attributes:
    • name: The name of the configuration setting.
    • slug: A URL-friendly version of the name, often used for lookups.
    • configuration_type: The type or category of the configuration setting.
    • description: A brief explanation of the configuration setting.
    • resource: The associated resource or model.
    • active: A boolean flag to indicate if the setting is active.
    • data: The value or content of the configuration setting, likely stored as a JSON or text field.

5. Index Page Customization

• index do
  • The index block customizes the list view for ConfigurationSetting records in the admin interface.
  • Columns Displayed:
    • selectable_column: Allows the selection of multiple rows for batch actions (even though batch actions might not be enabled here).
    • id_column: Displays the unique ID of each configuration setting.
    • slug: Shows the slug of the setting.
    • name: Displays the name of the setting.
    • configuration_type: Shows the type or category of the configuration.
    • description: Provides a brief description of the setting.
    • active: Indicates whether the setting is active.

Summary:

• Configuration Settings Management: This ActiveAdmin setup allows administrators to manage ConfigurationSetting records, focusing on essential attributes like name, slug, type, and status.
• Preventing Deletion: The destroy action is disabled, likely to safeguard against the accidental removal of critical settings.
• Intuitive Interface: The sorting by name and organized index page make it easy for administrators to find and manage specific settings.
• Permitted Parameters: The setup ensures that only the relevant attributes can be modified, protecting against unintended changes.