airdrop_recipients.rb

[geekelo]

FILE

ActiveAdmin.register AirdropRecipient do

  actions :all, except: :destroy

  includes :airdrop

  menu parent: 'Stores', label: 'Airdrop Recipients'

  # preserve_default_filters!
  filter :id_eq, as: :string, label: 'ID'
  filter :airdrop_id_eq, as: :string, label: 'Airdrop ID'
  filter :crypto_transfer_id_eq, as: :string, label: 'Crypto Transfer ID'
  filter :wallet_address_eq, as: :string, label: 'Wallet Address'
  filter :original_wallet_address_eq, as: :string, label: 'Original Wallet Address'
  filter :status, as: :select, collection: AirdropRecipient::AIRDROP_RECIPIENT_STATUS
  filter :active

  permit_params :airdrop, :crypto_transfer, :participation, :ref1, :balance, :wallet_address, :token_balance,
                :transaction_hash, :status, :sent_at, :active

  index do
    selectable_column
    id_column
    column :airdrop
    column :crypto_transfer
    column :user_email do |airdrop_recipient|
      airdrop_recipient.user_email
    end
    column :token_balance
    column :wallet_address

    column :status
    column :api_request_body do |airdrop_recipient|
      unless airdrop_recipient.crypto_transfer&.complete?
        wallet_id = airdrop_recipient.airdrop.store.default_crypto_api_wallet&.external_id
        token = airdrop_recipient.airdrop.token_symbol
        json_request_body = {
          walletId: "#{wallet_id}",
          amount: "#{airdrop_recipient.token_balance}",
          token: "#{token}",
          destinationAddress: "#{airdrop_recipient.wallet_address}",
          externalId: "#{airdrop_recipient.crypto_transfer&.id}",
          chainId: ENV.fetch('POLYGON_CHAIN_ID').to_i
        }.to_json
        "<code>#{json_request_body}</code>".html_safe
      end
    end
    column :participation
    column :balance
    column :ref1
    column :original_wallet_address
    column :created_at
    column :updated_at
  end

  csv do
    column :id
    column :airdrop
    column :crypto_transfer
    column :user_email do |airdrop_recipient|
      airdrop_recipient.user_email
    end
    column :participation
    column :balance
    column :ref1
    column :token_balance
    column :wallet_address
    column :original_wallet_address    
    column :status
    column :created_at
    column :updated_at
    column :api_request_body do |airdrop_recipient|
      unless airdrop_recipient.crypto_transfer&.complete?
        wallet_id = airdrop_recipient.airdrop.store.default_crypto_api_wallet&.external_id
        token = airdrop_recipient.airdrop.token_symbol
        {
          walletId: "#{wallet_id}",
          amount: "#{airdrop_recipient.token_balance}",
          token: "#{token}",
          destinationAddress: "#{airdrop_recipient.wallet_address}",
          externalId: "#{airdrop_recipient.crypto_transfer&.id}",
          chainId: ENV.fetch('POLYGON_CHAIN_ID').to_i
        }.to_json
      end
    end
  end

  show do
    default_main_content
    attributes_table do
      row 'User Email' do |airdrop_recipient|
        airdrop_recipient.user_email
      end
    end
  end
end

[geekelo]

This code configures the admin interface for managing AirdropRecipient records in an ActiveAdmin panel within a Ruby on Rails application. Here's a detailed breakdown of what this file does:

File: airdrop_recipient.rb

1. ActiveAdmin.register AirdropRecipient do

• Registers the AirdropRecipient model with ActiveAdmin, creating an admin interface for managing AirdropRecipient records.

2. actions :all, except: :destroy

• Enables all default CRUD actions except for the destroy action. This prevents users from deleting AirdropRecipient records via the admin interface.

3. includes :airdrop

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

4. menu parent: 'Stores', label: 'Airdrop Recipients'

• Places the AirdropRecipient resource under the Stores menu with the label Airdrop Recipients in the ActiveAdmin interface. This organizes the admin panel by grouping related resources together.

5. filter :...

• Adds custom filters to the index page for the AirdropRecipient records. These filters allow admins to search and filter records by various attributes, such as ID, Airdrop ID, Crypto Transfer ID, Wallet Address, Original Wallet Address, Status, and Active status.
• Filters use different input types, such as text fields (:string) and dropdowns (:select).

6. permit_params :...

• Specifies the parameters allowed to be mass-assigned through the ActiveAdmin interface. This includes attributes like airdrop, crypto_transfer, participation, wallet_address, status, etc.
• This ensures only permitted attributes can be modified, protecting against mass-assignment vulnerabilities.

7. index do ... end

• Customizes the index page (the list view) for AirdropRecipient records.
• Includes columns for selection, id, airdrop, crypto_transfer, user_email, token_balance, wallet_address, status, api_request_body, participation, balance, ref1, original_wallet_address, and timestamps (created_at, updated_at).
• The user_email and api_request_body columns are customized using blocks, providing specific logic for how these values are displayed:
  • user_email is fetched from the associated record.
  • api_request_body generates a JSON string representing an API request, but only if the associated crypto_transfer is not complete.

8. csv do ... end

• Customizes the CSV export functionality for AirdropRecipient records.
• Specifies which columns should be included in the CSV file, including id, airdrop, crypto_transfer, user_email, and more.
• Like the index page, the api_request_body is conditionally generated and included in the CSV export.

9. show do ... end

• Customizes the show page (the detailed view of a single AirdropRecipient record).
• Uses default_main_content to render the default content and adds an attributes_table to display the user_email attribute.

Summary:

• This file sets up an admin interface for managing AirdropRecipient records.
• It includes customizations for listing, filtering, showing, and exporting records.
• Special attention is given to generating and displaying the user_email and api_request_body attributes.
• The destroy action is disabled, preserving data integrity by preventing deletion of records through the admin interface.

This setup provides a robust and customized interface for managing airdrop recipients in the application, with careful attention to security and performance.