module ActiveStorage::Attached::Macros

(i.e. destroyed) whenever the record is destroyed.
If the +:dependent+ option isn't set, the attachment will be purged

proxy that provides the dynamic proxy to the associations and factory methods, like +attach+.
The system has been designed to having you go through the ActiveStorage::Attached::One

most circumstances.
and +avatar_blob+. But you shouldn't need to work with these associations directly in
ActiveStorage::Blob record. These associations are available as +avatar_attachment+
ActiveStorage::Attachment record and a +has_one-through+ association to a
Under the covers, this relationship is implemented as a +has_one+ association to a

User.with_attached_avatar

To avoid N+1 queries, you can include the attached blobs in your query like so:

care of the mapping between your records and the attachment.
There is no column defined on the model side, Active Storage takes

end
has_one_attached :avatar
class User < ActiveRecord::Base

Specifies the relation between a single attachment and the model.

def has_one_attached(name, dependent: :purge_later)
  class_eval <<-CODE, __FILE__, __LINE__ + 1
    def #{name}
      @active_storage_attached_#{name} ||= ActiveStorage::Attached::One.new("#{name}", self, dependent: #{dependent == :purge_later ? ":purge_later" : "false"})
    end
    def #{name}=(attachable)
      #{name}.attach(attachable)
    end
  CODE
  has_one :"#{name}_attachment", -> { where(name: name) }, class_name: "ActiveStorage::Attachment", as: :record, inverse_of: :record, dependent: false
  has_one :"#{name}_blob", through: :"#{name}_attachment", class_name: "ActiveStorage::Blob", source: :blob
  scope :"with_attached_#{name}", -> { includes("#{name}_attachment": :blob) }
  if dependent == :purge_later
    after_destroy_commit { public_send(name).purge_later }
  else
    before_destroy { public_send(name).detach }
  end
end