crypto_orders.rb

[geekelo]

FILE

ActiveAdmin.register CryptoOrder do
  actions :all, except: :destroy
  permit_params :status
  includes :user, :crypto_transfer, :wallet_address

  config.sort_order = 'created_at_desc'

  menu parent: 'Transactions', label: 'Crypto Orders'

  # 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 :user_id, :crypto_transfer_id, :wallet_address_id, :external_id, :order_type, :destination, :purchase_amount, :source_amount, :source_currency, :destination_currency, :usd_source_amount, :usd_purchase_amount, :wallet_type, :auth_code_requested, :error_category, :failure_reason, :payment_network_code, :internal_error_code, :status, :active
  #
  # or
  #
  # permit_params do
  #   permitted = [:user_id, :crypto_transfer_id, :wallet_address_id, :external_id, :order_type, :destination, :purchase_amount, :source_amount, :source_currency, :destination_currency, :usd_source_amount, :usd_purchase_amount, :wallet_type, :auth_code_requested, :error_category, :failure_reason, :payment_network_code, :internal_error_code, :status, :active]
  #   permitted << :other if params[:action] == 'create' && current_user.admin?
  #   permitted
  # end

end

[geekelo]

This file configures the ActiveAdmin interface for managing CryptoOrder records, with a focus on providing all actions except for deletion. The setup includes menu placement, permitted parameters, and sorting configuration.

File: crypto_order.rb

1. Actions Configuration

• actions :all, except: :destroy
  • This line allows all standard CRUD actions (index, show, new, create, edit, update) except for destroy. This restriction may be intended to prevent accidental deletion of important transaction records.

2. Permitted Parameters

• permit_params
  • This method specifies which parameters can be modified through the admin interface. The list of permitted parameters ensures that only relevant and safe attributes are mass-assigned during record creation or update.
  • Attributes:
    • user_id: The ID of the associated user.
    • crypto_transfer_id: The ID of the associated crypto transfer.
    • wallet_address_id: The ID of the associated wallet address.
    • external_id: An external identifier for the order.
    • order_type: The type of the crypto order.
    • destination: The destination for the crypto transfer.
    • purchase_amount: The amount of cryptocurrency being purchased.
    • source_amount: The source amount in fiat or another currency.
    • source_currency: The currency used for the source amount.
    • destination_currency: The currency being transferred to.
    • usd_source_amount: The source amount in USD.
    • usd_purchase_amount: The purchase amount in USD.
    • wallet_type: The type of wallet being used.
    • auth_code_requested: Whether an authorization code was requested.
    • error_category: The category of any error that occurred.
    • failure_reason: The reason for failure if the order failed.
    • payment_network_code: The code for the payment network.
    • internal_error_code: An internal code for any errors.
    • status: The status of the crypto order.
    • active: Whether the order is currently active.

3. Includes Configuration

• includes :user, :crypto_transfer, :wallet_address
  • This line preloads the associated user, crypto_transfer, and wallet_address models to optimize database queries and improve the performance of the admin interface, particularly when listing or viewing individual records.

4. Sorting Configuration

• config.sort_order = 'created_at_desc'
  • The default sorting order is set to display the most recently created records first. This is useful in transactional systems where recent activity is often the most relevant.

5. Menu Configuration

• menu parent: 'Transactions', label: 'Crypto Orders'
  • The CryptoOrder resource is placed under the "Transactions" menu with the label "Crypto Orders." This categorizes the resource appropriately within the admin interface, making it easier to navigate.

Summary:

• Transaction Management: This ActiveAdmin configuration is set up for managing CryptoOrder records, providing a detailed interface for viewing and updating transaction-related data.
• Preventing Deletion: The deletion action is disabled, likely to prevent the accidental removal of crucial transaction records.
• Optimized Performance: The includes directive improves performance by reducing the number of database queries.
• Clear Organization: The CryptoOrder resource is organized under the "Transactions" menu, which helps administrators find and manage crypto-related transactions more easily.
• Comprehensive Permitted Parameters: The extensive list of permitted parameters ensures that the system is flexible enough to handle various aspects of a crypto order, while also maintaining security by controlling what can be modified.