admin_users.rb

[geekelo]

FILE

ActiveAdmin.register AdminUser do
  permit_params :email, :password, :password_confirmation, role_ids: []
  includes :roles
  actions :all, except: :destroy

  menu parent: 'Configuration', label: 'Admin Users'

  index do
    selectable_column
    id_column
    column :email
    column :created_at
    column :roles
    actions
  end

  filter :email
  filter :created_at

  show do
    attributes_table do
      row :email
      row :created_at
      row :roles
    end
  end

  form do |f|
    f.inputs do
      f.input :email
      if f.object.new_record?
        f.input :password
        f.input :password_confirmation
      end
      f.input :roles, as: :check_boxes, :collection => AdminRole.all
    end
    f.actions
  end

  action_item :discard, only: :show do
    link_to 'Discard User', discard_admin_admin_user_path(resource), method: :get
  end

  member_action :discard, method: :get do
    resource.discard
    flash[:notice] = "User discarded successfully."
    redirect_to [:admin, :admin_users]
  end

end

[geekelo]

This code is a configuration file for managing AdminUser records in an ActiveAdmin interface within a Ruby on Rails application. Here's a detailed breakdown of what's happening in this file:

File: admin_user.rb

1. ActiveAdmin.register AdminUser do

• Registers the AdminUser model with ActiveAdmin, allowing an admin interface to be generated for managing AdminUser records.

2. permit_params :email, :password, :password_confirmation, role_ids: []

• Specifies the parameters allowed to be mass-assigned through the ActiveAdmin interface. The permitted parameters here are email, password, password_confirmation, and an array of role_ids.
• This setup allows the AdminUser to update their email and password and assign roles through the admin interface.

3. includes :roles

• Eager loads the associated roles when querying AdminUser records, improving performance by reducing the number of database queries.

4. actions :all, except: :destroy

• Enables all default CRUD actions except for the destroy action, which prevents users from being deleted through the admin interface. This is often done to preserve data integrity or to implement a soft-delete mechanism.

5. menu parent: 'Configuration', label: 'Admin Users'

• Configures the menu structure in the ActiveAdmin interface, placing the AdminUser resource under the Configuration menu with the label Admin Users.

6. index do ... end

• Customizes the index page (the list view of AdminUser records).
• Includes columns for selection (selectable_column), id, email, created_at, and roles.
• The actions call adds default action buttons (like view, edit) for each record.

7. filter :email, filter :created_at

• Adds filters to the index page, allowing the admin to filter AdminUser records by email and created_at.

8. show do ... end

• Customizes the show page (the detailed view of a single AdminUser record).
• Displays email, created_at, and roles in a table format.

9. form do |f| ... end

• Customizes the form for creating and editing AdminUser records.
• Includes inputs for email, password, password_confirmation, and a checkbox list for assigning roles (AdminRole.all is used to fetch all available roles).
• Password fields are only shown when creating a new user (f.object.new_record? checks if the form is for a new record).

10. action_item :discard, only: :show do ... end

• Adds a custom action button to the show page for discarding (soft-deleting) a user. The button is labeled "Discard User" and links to the custom discard action.

11. member_action :discard, method: :get do ... end

• Defines a custom action for discarding a user.
• Calls the discard method on the AdminUser model (assuming it's implemented with a gem like discard for soft-deleting).
• Sets a flash message "User discarded successfully." and redirects back to the AdminUser index page.

Summary:

• This file configures the ActiveAdmin interface for managing AdminUser records, including customizations for listing, filtering, showing, and editing users.
• The interface supports assigning roles to users, updating their email and password, and includes a custom action for soft-deleting users (discard).
• The destroy action is disabled, so users cannot be permanently deleted through the admin interface.

This setup provides a comprehensive admin interface for managing admin users while maintaining data integrity and security.