discourse/plugins/poll/lib/post_validator.rb

# frozen_string_literal: true

module DiscoursePoll
  class PostValidator
    def initialize(post)
      @post = post
    end

    def validate_post
      min_trust_level = SiteSetting.poll_minimum_trust_level_to_create

      if (@post.acting_user && (@post.acting_user.staff? || @post.acting_user.trust_level >= TrustLevel[min_trust_level])) || @post.topic&.pm_with_non_human_user?
        true
      else
        @post.errors.add(:base, I18n.t("poll.insufficient_rights_to_create"))
        false
      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-03 08:17:27 +10:00			`# frozen_string_literal: true`

FEATURE: introduces minimum trust level for polls (#5391) * FEATURE: introduces minimum trust level for polls This commit makes `poll_enabled` less misleading and introduces `poll_minimum_trust_level_to_create`. If poll are enabled they will always be cooked, and if you have the required trust level you can create polls. As a side effect, it also fixes a bug where rebaking a post created by staff member when `poll_enabled=false` would end up not cooking it. It also adds more tests to ensure settings are respected. * admins should be whitelisted * checks for admin in post validation * test for >= instead of == trust level 2017-12-04 14:47:11 +01:00			`module DiscoursePoll`
			`class PostValidator`
			`def initialize(post)`
			`@post = post`
			`end`

			`def validate_post`
			`min_trust_level = SiteSetting.poll_minimum_trust_level_to_create`

FIX: Validate post's polls as acting user (#16638) It used to validate the post from the perspective of the user who created the post. That did not work well when an admin attempted to add a poll to a post created by a user who cannot create posts because it said the user cannot create polls. The problem was that it used post.user for the validation process instead of post.acting_user. 2022-05-05 09:54:10 +03:00			`if (@post.acting_user && (@post.acting_user.staff? \|\| @post.acting_user.trust_level >= TrustLevel[min_trust_level])) \|\| @post.topic&.pm_with_non_human_user?`
FEATURE: automatically close a poll on a given date and time 2018-05-03 02:12:19 +02:00			`true`
			`else`
			`@post.errors.add(:base, I18n.t("poll.insufficient_rights_to_create"))`
			`false`
FEATURE: introduces minimum trust level for polls (#5391) * FEATURE: introduces minimum trust level for polls This commit makes `poll_enabled` less misleading and introduces `poll_minimum_trust_level_to_create`. If poll are enabled they will always be cooked, and if you have the required trust level you can create polls. As a side effect, it also fixes a bug where rebaking a post created by staff member when `poll_enabled=false` would end up not cooking it. It also adds more tests to ensure settings are respected. * admins should be whitelisted * checks for admin in post validation * test for >= instead of == trust level 2017-12-04 14:47:11 +01:00			`end`
			`end`
			`end`
			`end`