Spec-Zone.ru › Ruby on Rails 8.1

module ActiveStorage::Attached::Model

Модель вложений Active Storage

Предоставляет DSL уровня класса для объявления вложений модели Active Record.

Открытые методы экземпляра

*_attachment () Показать исходный код
# File activestorage/lib/active_storage/attached/model.rb, line 13
    

Возвращает вложение для has_one_attached.

User.last.avatar_attachment
*_attachments () Показать исходный код
# File activestorage/lib/active_storage/attached/model.rb, line 20
    

Возвращает вложения для has_many_attached.

Gallery.last.photos_attachments
*_blob () Показать исходный код
# File activestorage/lib/active_storage/attached/model.rb, line 27
    

Возвращает blob для вложения has_one_attached.

User.last.avatar_blob
*_blobs () Показать исходный код
# File activestorage/lib/active_storage/attached/model.rb, line 34
    

Возвращает blobs для вложений has_many_attached.

Gallery.last.photos_blobs
has_many_attached (name, dependent: :purge_later, service: nil, strict_loading: false) { |reflection| ... } Показать исходный код
# File activestorage/lib/active_storage/attached/model.rb, line 210
      def has_many_attached(name, dependent: :purge_later, service: nil, strict_loading: false)
        Attached::Model.validate_service_configuration(service, self, name) unless service.is_a?(Proc)

        generated_association_methods.class_eval <<-CODE, __FILE__, __LINE__ + 1
          # frozen_string_literal: true
          def #{name}
            @active_storage_attached ||= {}
            @active_storage_attached[:#{name}] ||= ActiveStorage::Attached::Many.new("#{name}", self)
          end

          def #{name}=(attachables)
            attachables = Array(attachables).compact_blank
            pending_uploads = attachment_changes["#{name}"].try(:pending_uploads)

            attachment_changes["#{name}"] = if attachables.none?
              ActiveStorage::Attached::Changes::DeleteMany.new("#{name}", self)
            else
              ActiveStorage::Attached::Changes::CreateMany.new("#{name}", self, attachables, pending_uploads: pending_uploads)
            end
          end
        CODE

        has_many :"#{name}_attachments", -> { where(name: name) }, as: :record, class_name: "ActiveStorage::Attachment", inverse_of: :record, dependent: :destroy, strict_loading: strict_loading
        has_many :"#{name}_blobs", through: :"#{name}_attachments", class_name: "ActiveStorage::Blob", source: :blob, strict_loading: strict_loading

        scope :"with_attached_#{name}", -> {
          if ActiveStorage.track_variants
            includes("#{name}_attachments": { blob: {
              variant_records: { image_attachment: :blob },
              preview_image_attachment: { blob: { variant_records: { image_attachment: :blob } } }
            } })
          else
            includes("#{name}_attachments": :blob)
          end
        }

        after_save { attachment_changes[name.to_s]&.save }

        after_commit(on: %i[ create update ]) { attachment_changes.delete(name.to_s).try(:upload) }

        reflection = ActiveRecord::Reflection.create(
          :has_many_attached,
          name,
          nil,
          { dependent: dependent, service_name: service },
          self
        )
        yield reflection if block_given?
        ActiveRecord::Reflection.add_attachment_reflection(self, name, reflection)
      end

Задает связь между несколькими вложениями и моделью.

class Gallery < ApplicationRecord
  has_many_attached :photos
end

На стороне модели столбцы не определяются: Active Storage берет на себя сопоставление записей и вложений.

Внутри эта связь реализована как ассоциация has_many с записью ActiveStorage::Attachment и ассоциация has_many-through с записью ActiveStorage::Blob. Эти ассоциации доступны как photos_attachments и photos_blobs. Однако в большинстве случаев вам не придется работать с ними напрямую.

Вместо этого has_many_attached создает прокси ActiveStorage::Attached::Many, предоставляющий доступ к ассоциациям и фабричным методам, например attach:

user.photos.attach(uploaded_file)

По умолчанию для параметра :dependent используется значение :purge_later. Это означает, что при уничтожении записи вложения будут удалены (то есть уничтожены) в фоновом режиме. Если в приложении не задан адаптер очереди ActiveJob::Backend, вместо этого установите значение purge.

Если для вложения требуется сервис, отличный от глобально настроенного, передайте параметр :service. Например:

class Gallery < ActiveRecord::Base
  has_many_attached :photos, service: :s3
end

:service также можно задать как proc; он будет вызван с экземпляром модели:

class Gallery < ActiveRecord::Base
  has_many_attached :photos, service: ->(gallery) { gallery.personal? ? :personal_s3 : :s3 }
end

Чтобы избежать запросов N+1, можно включить вложенные blobs в запрос следующим образом:

Gallery.where(user: Current.user).with_attached_photos

Если необходимо включить strict_loading, чтобы запретить отложенную загрузку вложений, передайте параметр :strict_loading. Например:

class Gallery < ApplicationRecord
  has_many_attached :photos, strict_loading: true
end

Примечание: Active Storage использует полиморфные ассоциации, в которых, в свою очередь, в базе данных сохраняются имена классов. При переименовании классов, использующих has_many, не забудьте также обновить имена классов в столбце полиморфного типа active_storage_attachments.record_type соответствующих строк.

has_one_attached (name, dependent: :purge_later, service: nil, strict_loading: false) { |reflection| ... } Показать исходный код
# File activestorage/lib/active_storage/attached/model.rb, line 108
      def has_one_attached(name, dependent: :purge_later, service: nil, strict_loading: false)
        Attached::Model.validate_service_configuration(service, self, name) unless service.is_a?(Proc)

        generated_association_methods.class_eval <<-CODE, __FILE__, __LINE__ + 1
          # frozen_string_literal: true
          def #{name}
            @active_storage_attached ||= {}
            @active_storage_attached[:#{name}] ||= ActiveStorage::Attached::One.new("#{name}", self)
          end

          def #{name}=(attachable)
            attachment_changes["#{name}"] =
              if attachable.nil? || attachable == ""
                ActiveStorage::Attached::Changes::DeleteOne.new("#{name}", self)
              else
                ActiveStorage::Attached::Changes::CreateOne.new("#{name}", self, attachable)
              end
          end
        CODE

        has_one :"#{name}_attachment", -> { where(name: name) }, class_name: "ActiveStorage::Attachment", as: :record, inverse_of: :record, dependent: :destroy, strict_loading: strict_loading
        has_one :"#{name}_blob", through: :"#{name}_attachment", class_name: "ActiveStorage::Blob", source: :blob, strict_loading: strict_loading

        scope :"with_attached_#{name}", -> {
          if ActiveStorage.track_variants
            includes("#{name}_attachment": { blob: {
              variant_records: { image_attachment: :blob },
              preview_image_attachment: { blob: { variant_records: { image_attachment: :blob } } }
            } })
          else
            includes("#{name}_attachment": :blob)
          end
        }

        after_save { attachment_changes[name.to_s]&.save }

        after_commit(on: %i[ create update ]) { attachment_changes.delete(name.to_s).try(:upload) }

        reflection = ActiveRecord::Reflection.create(
          :has_one_attached,
          name,
          nil,
          { dependent: dependent, service_name: service },
          self
        )
        yield reflection if block_given?
        ActiveRecord::Reflection.add_attachment_reflection(self, name, reflection)
      end

Задает связь между одним вложением и моделью.

class User < ApplicationRecord
  has_one_attached :avatar
end

На стороне модели столбец не определяется: Active Storage берет на себя сопоставление записей и вложения.

Внутри эта связь реализована как ассоциация has_one с записью ActiveStorage::Attachment и ассоциация has_one-through с записью ActiveStorage::Blob. Эти ассоциации доступны как avatar_attachment и avatar_blob. Однако в большинстве случаев вам не придется работать с ними напрямую.

Вместо этого has_one_attached создает прокси ActiveStorage::Attached::One, предоставляющий доступ к ассоциациям и фабричным методам, например attach:

user.avatar.attach(uploaded_file)

По умолчанию для параметра :dependent используется значение :purge_later. Это означает, что при уничтожении записи вложение будет удалено (то есть уничтожено) в фоновом режиме. Если в приложении не задан адаптер очереди ActiveJob::Backend, вместо этого установите значение purge.

Если для вложения требуется сервис, отличный от глобально настроенного, передайте параметр :service. Например:

class User < ActiveRecord::Base
  has_one_attached :avatar, service: :s3
end

:service также можно задать как proc; он будет вызван с экземпляром модели:

class User < ActiveRecord::Base
  has_one_attached :avatar, service: ->(user) { user.in_europe_region? ? :s3_europe : :s3_usa }
end

Чтобы избежать запросов N+1, можно включить вложенные blobs в запрос следующим образом:

User.with_attached_avatar

Если необходимо включить strict_loading, чтобы запретить отложенную загрузку вложения, передайте параметр :strict_loading. Например:

class User < ApplicationRecord
  has_one_attached :avatar, strict_loading: true
end

Примечание: Active Storage использует полиморфные ассоциации, в которых, в свою очередь, в базе данных сохраняются имена классов. При переименовании классов, использующих has_one_attached, не забудьте также обновить имена классов в столбце полиморфного типа active_storage_attachments.record_type соответствующих строк.

with_attached_* () Показать исходный код
# File activestorage/lib/active_storage/attached/model.rb, line 54
    class_methods do
      # Specifies the relation between a single attachment and the model.
      #
      #   class User < ApplicationRecord
      #     has_one_attached :avatar
      #   end
      #
      # There is no column defined on the model side, Active Storage takes
      # care of the mapping between your records and the attachment.
      #
      # Under the covers, this relationship is implemented as a +has_one+ association to an
      # ActiveStorage::Attachment record and a +has_one-through+ association to an
      # ActiveStorage::Blob record. These associations are available as +avatar_attachment+
      # and +avatar_blob+. But you shouldn't need to work with these associations directly in
      # most circumstances.
      #
      # Instead, +has_one_attached+ generates an ActiveStorage::Attached::One proxy to
      # provide access to the associations and factory methods, like +attach+:
      #
      #   user.avatar.attach(uploaded_file)
      #
      # The +:dependent+ option defaults to +:purge_later+. This means the attachment will be
      # purged (i.e. destroyed) in the background whenever the record is destroyed.
      # If an ActiveJob::Backend queue adapter is not set in the application set it to
      # +purge+ instead.
      #
      # If you need the attachment to use a service which differs from the globally configured one,
      # pass the +:service+ option. For example:
      #
      #   class User < ActiveRecord::Base
      #     has_one_attached :avatar, service: :s3
      #   end
      #
      # +:service+ can also be specified as a proc, and it will be called with the model instance:
      #
      #   class User < ActiveRecord::Base
      #     has_one_attached :avatar, service: ->(user) { user.in_europe_region? ? :s3_europe : :s3_usa }
      #   end
      #
      # To avoid N+1 queries, you can include the attached blobs in your query like so:
      #
      #   User.with_attached_avatar
      #
      # If you need to enable +strict_loading+ to prevent lazy loading of attachment,
      # pass the +:strict_loading+ option. You can do:
      #
      #   class User < ApplicationRecord
      #     has_one_attached :avatar, strict_loading: true
      #   end
      #
      # Note: Active Storage relies on polymorphic associations, which in turn store class names in the database.
      # When renaming classes that use <tt>has_one_attached</tt>, make sure to also update the class names in the
      # <tt>active_storage_attachments.record_type</tt> polymorphic type column of
      # the corresponding rows.
      def has_one_attached(name, dependent: :purge_later, service: nil, strict_loading: false)
        Attached::Model.validate_service_configuration(service, self, name) unless service.is_a?(Proc)

        generated_association_methods.class_eval <<-CODE, __FILE__, __LINE__ + 1
          # frozen_string_literal: true
          def #{name}
            @active_storage_attached ||= {}
            @active_storage_attached[:#{name}] ||= ActiveStorage::Attached::One.new("#{name}", self)
          end

          def #{name}=(attachable)
            attachment_changes["#{name}"] =
              if attachable.nil? || attachable == ""
                ActiveStorage::Attached::Changes::DeleteOne.new("#{name}", self)
              else
                ActiveStorage::Attached::Changes::CreateOne.new("#{name}", self, attachable)
              end
          end
        CODE

        has_one :"#{name}_attachment", -> { where(name: name) }, class_name: "ActiveStorage::Attachment", as: :record, inverse_of: :record, dependent: :destroy, strict_loading: strict_loading
        has_one :"#{name}_blob", through: :"#{name}_attachment", class_name: "ActiveStorage::Blob", source: :blob, strict_loading: strict_loading

        scope :"with_attached_#{name}", -> {
          if ActiveStorage.track_variants
            includes("#{name}_attachment": { blob: {
              variant_records: { image_attachment: :blob },
              preview_image_attachment: { blob: { variant_records: { image_attachment: :blob } } }
            } })
          else
            includes("#{name}_attachment": :blob)
          end
        }

        after_save { attachment_changes[name.to_s]&.save }

        after_commit(on: %i[ create update ]) { attachment_changes.delete(name.to_s).try(:upload) }

        reflection = ActiveRecord::Reflection.create(
          :has_one_attached,
          name,
          nil,
          { dependent: dependent, service_name: service },
          self
        )
        yield reflection if block_given?
        ActiveRecord::Reflection.add_attachment_reflection(self, name, reflection)
      end

      # Specifies the relation between multiple attachments and the model.
      #
      #   class Gallery < ApplicationRecord
      #     has_many_attached :photos
      #   end
      #
      # There are no columns defined on the model side, Active Storage takes
      # care of the mapping between your records and the attachments.
      #
      # Under the covers, this relationship is implemented as a +has_many+ association to an
      # ActiveStorage::Attachment record and a +has_many-through+ association to an
      # ActiveStorage::Blob record. These associations are available as +photos_attachments+
      # and +photos_blobs+. But you shouldn't need to work with these associations directly in
      # most circumstances.
      #
      # Instead, +has_many_attached+ generates an ActiveStorage::Attached::Many proxy to
      # provide access to the associations and factory methods, like +attach+:
      #
      #   user.photos.attach(uploaded_file)
      #
      # The +:dependent+ option defaults to +:purge_later+. This means the attachments will be
      # purged (i.e. destroyed) in the background whenever the record is destroyed.
      # If an ActiveJob::Backend queue adapter is not set in the application set it to
      # +purge+ instead.
      #
      # If you need the attachment to use a service which differs from the globally configured one,
      # pass the +:service+ option. For example:
      #
      #   class Gallery < ActiveRecord::Base
      #     has_many_attached :photos, service: :s3
      #   end
      #
      # +:service+ can also be specified as a proc, and it will be called with the model instance:
      #
      #   class Gallery < ActiveRecord::Base
      #     has_many_attached :photos, service: ->(gallery) { gallery.personal? ? :personal_s3 : :s3 }
      #   end
      #
      # To avoid N+1 queries, you can include the attached blobs in your query like so:
      #
      #   Gallery.where(user: Current.user).with_attached_photos
      #
      # If you need to enable +strict_loading+ to prevent lazy loading of attachments,
      # pass the +:strict_loading+ option. You can do:
      #
      #   class Gallery < ApplicationRecord
      #     has_many_attached :photos, strict_loading: true
      #   end
      #
      # Note: Active Storage relies on polymorphic associations, which in turn store class names in the database.
      # When renaming classes that use <tt>has_many</tt>, make sure to also update the class names in the
      # <tt>active_storage_attachments.record_type</tt> polymorphic type column of
      # the corresponding rows.
      def has_many_attached(name, dependent: :purge_later, service: nil, strict_loading: false)
        Attached::Model.validate_service_configuration(service, self, name) unless service.is_a?(Proc)

        generated_association_methods.class_eval <<-CODE, __FILE__, __LINE__ + 1
          # frozen_string_literal: true
          def #{name}
            @active_storage_attached ||= {}
            @active_storage_attached[:#{name}] ||= ActiveStorage::Attached::Many.new("#{name}", self)
          end

          def #{name}=(attachables)
            attachables = Array(attachables).compact_blank
            pending_uploads = attachment_changes["#{name}"].try(:pending_uploads)

            attachment_changes["#{name}"] = if attachables.none?
              ActiveStorage::Attached::Changes::DeleteMany.new("#{name}", self)
            else
              ActiveStorage::Attached::Changes::CreateMany.new("#{name}", self, attachables, pending_uploads: pending_uploads)
            end
          end
        CODE

        has_many :"#{name}_attachments", -> { where(name: name) }, as: :record, class_name: "ActiveStorage::Attachment", inverse_of: :record, dependent: :destroy, strict_loading: strict_loading
        has_many :"#{name}_blobs", through: :"#{name}_attachments", class_name: "ActiveStorage::Blob", source: :blob, strict_loading: strict_loading

        scope :"with_attached_#{name}", -> {
          if ActiveStorage.track_variants
            includes("#{name}_attachments": { blob: {
              variant_records: { image_attachment: :blob },
              preview_image_attachment: { blob: { variant_records: { image_attachment: :blob } } }
            } })
          else
            includes("#{name}_attachments": :blob)
          end
        }

        after_save { attachment_changes[name.to_s]&.save }

        after_commit(on: %i[ create update ]) { attachment_changes.delete(name.to_s).try(:upload) }

        reflection = ActiveRecord::Reflection.create(
          :has_many_attached,
          name,
          nil,
          { dependent: dependent, service_name: service },
          self
        )
        yield reflection if block_given?
        ActiveRecord::Reflection.add_attachment_reflection(self, name, reflection)
      end
    end

Включает вложенные blobs в запрос, чтобы избежать запросов N+1.

Если включен ActiveStorage.track_variants, в запрос также будут включены запись вариантов и связанные с ней blobs.

User.with_attached_avatar

Для has_many_attached используйте форму множественного числа:

Gallery.with_attached_photos

© 2004–2021 David Heinemeier Hansson
Licensed under the MIT License.

Spec-Zone.ru

Настройки Оффлайн Что нового Помощь О нас
Spec-Zone .ru
спецификации, руководства, описания, API