discourse/app/jobs/regular/delete_topic.rb

# frozen_string_literal: true

module Jobs
  class DeleteTopic < ::Jobs::TopicTimerBase
    def execute_timer_action(topic_timer, topic)
      if Guardian.new(topic_timer.user).can_delete?(topic)
        first_post = topic.ordered_posts.first

        PostDestroyer.new(
          topic_timer.user,
          first_post,
          context: I18n.t("topic_statuses.auto_deleted_by_timer"),
        ).destroy

        topic_timer.trash!(Discourse.system_user)
      end
    end
  end
end
DEV: enable frozen string literal on all files This reduces chances of errors where consumers of strings mutate inputs and reduces memory usage of the app. Test suite passes now, but there may be some stuff left, so we will run a few sites on a branch prior to merging 2019-05-02 17:17:27 -05:00			`# frozen_string_literal: true`

FEATURE: set a timer to delete a topic 2017-05-11 11:52:15 -05:00			`module Jobs`
DEV: Change Topic Timer from enqueue_at scheduled jobs to incrementally executed jobs (#11698) Moves the topic timer jobs from being scheduled ahead of time with enqueue_at to a 5 minute scheduled run like bookmark reminders, in a new job called Jobs::EnqueueTopicTimers. Backwards compatibility is maintained by checking if an existing topic timer job is enqueued in sidekiq for the timer, and if it is not running it inside the new job. The functionality to close/open a topic if it is in the opposite state still remains in the after_save block of TopicTimer, with further commentary, which is used for Open/Close Temporarily. This also removes the ensure_consistency! functionality of topic timers as it is no longer needed; the new job will always pick up the timers because they are not stored in a fragile state of sidekiq. 2021-01-18 21:30:58 -06:00			`class DeleteTopic < ::Jobs::TopicTimerBase`
			`def execute_timer_action(topic_timer, topic)`
rename topic_status_update to topic_timer 2017-05-11 17:23:18 -05:00			`if Guardian.new(topic_timer.user).can_delete?(topic)`
FEATURE: set a timer to delete a topic 2017-05-11 11:52:15 -05:00			`first_post = topic.ordered_posts.first`
DEV: Change Topic Timer from enqueue_at scheduled jobs to incrementally executed jobs (#11698) Moves the topic timer jobs from being scheduled ahead of time with enqueue_at to a 5 minute scheduled run like bookmark reminders, in a new job called Jobs::EnqueueTopicTimers. Backwards compatibility is maintained by checking if an existing topic timer job is enqueued in sidekiq for the timer, and if it is not running it inside the new job. The functionality to close/open a topic if it is in the opposite state still remains in the after_save block of TopicTimer, with further commentary, which is used for Open/Close Temporarily. This also removes the ensure_consistency! functionality of topic timers as it is no longer needed; the new job will always pick up the timers because they are not stored in a fragile state of sidekiq. 2021-01-18 21:30:58 -06:00
			`PostDestroyer.new(`
DEV: Apply syntax_tree formatting to `app/*` 2023-01-09 06:20:10 -06:00			`topic_timer.user,`
			`first_post,`
			`context: I18n.t("topic_statuses.auto_deleted_by_timer"),`
DEV: Change Topic Timer from enqueue_at scheduled jobs to incrementally executed jobs (#11698) Moves the topic timer jobs from being scheduled ahead of time with enqueue_at to a 5 minute scheduled run like bookmark reminders, in a new job called Jobs::EnqueueTopicTimers. Backwards compatibility is maintained by checking if an existing topic timer job is enqueued in sidekiq for the timer, and if it is not running it inside the new job. The functionality to close/open a topic if it is in the opposite state still remains in the after_save block of TopicTimer, with further commentary, which is used for Open/Close Temporarily. This also removes the ensure_consistency! functionality of topic timers as it is no longer needed; the new job will always pick up the timers because they are not stored in a fragile state of sidekiq. 2021-01-18 21:30:58 -06:00			`).destroy`

FIX: Delete topic timer after completion. 2017-05-11 21:28:51 -05:00			`topic_timer.trash!(Discourse.system_user)`
FEATURE: set a timer to delete a topic 2017-05-11 11:52:15 -05:00			`end`
			`end`
			`end`
rename topic_status_update to topic_timer 2017-05-11 17:23:18 -05:00			`end`