demarches-normaliennes/app/models/concerns/attachment_titre_identite_watermark_concern.rb

# frozen_string_literal: true

# Request a watermark on files attached to a `Champs::TitreIdentiteChamp`.
#
# We're using a class extension here, but we could as well have a periodic
# job that watermarks relevant attachments.
module AttachmentTitreIdentiteWatermarkConcern
  extend ActiveSupport::Concern

  included do
    after_create_commit :watermark_later
  end

  private

  def watermark_later
    blob&.watermark_later
  end
end
chore: enable freeze string literals by comment 2024-04-29 00:17:15 +02:00			`# frozen_string_literal: true`

active_storage: refactor concerns Follow-up of #5953. Refactor the concerns with two goals: - Getting closer from the way ActiveStorage adds its own hooks. Usually ActiveStorage does this using an `Attachment#after_create` hook, which then delegates to the blob to enqueue the job. - Enqueuing each job only once. By hooking on `Attachment#after_create`, we guarantee each job will be added only once. We then let the jobs themselves check if they are relevant or not, and retry or discard themselves if necessary. We also need to update the tests a bit, because Rails' `perform_enqueued_jobs(&block)` test helper doesn't honor the `retry_on` clause of jobs. Instead it forwards the exception to the caller – which makes the test fail. Instead we use the inline version of `perform_enqueued_jobs()`, without a block, which properly ignores errors catched by retry_on. 2021-03-11 14:42:57 +01:00			# Request a watermark on files attached to a `Champs::TitreIdentiteChamp`.
			`#`
			`# We're using a class extension here, but we could as well have a periodic`
			`# job that watermarks relevant attachments.`
			`module AttachmentTitreIdentiteWatermarkConcern`
			`extend ActiveSupport::Concern`

			`included do`
			`after_create_commit :watermark_later`
			`end`

			`private`

			`def watermark_later`
			`blob&.watermark_later`
			`end`
			`end`