a5b2d109d5
* Rename banned and comment_banned roles * Add data update script to rename roles containing 'ban' * Add named error for Suspended users * Update unidiomatic method names * Rename misc banned to suspended * Apply suggestions from code review Co-authored-by: Michael Kohl <me@citizen428.net> * Add unit tests for suspended methods This commit also adds TODO comments for removing banned and comment_banned from the codebase after data update scripts have successfully run on all of our Forems. Co-authored-by: Michael Kohl <me@citizen428.net>
43 lines
1 KiB
Ruby
43 lines
1 KiB
Ruby
class Role < ApplicationRecord
|
|
ROLES = %w[
|
|
admin
|
|
chatroom_beta_tester
|
|
codeland_admin
|
|
comment_suspended
|
|
mod_relations_admin
|
|
podcast_admin
|
|
restricted_liquid_tag
|
|
single_resource_admin
|
|
super_admin
|
|
support_admin
|
|
suspended
|
|
tag_moderator
|
|
tech_admin
|
|
trusted
|
|
warned
|
|
workshop_pass
|
|
].freeze
|
|
|
|
has_and_belongs_to_many :users, join_table: :users_roles # rubocop:disable Rails/HasAndBelongsToMany
|
|
|
|
belongs_to :resource,
|
|
polymorphic: true, optional: true
|
|
|
|
validates :resource_type,
|
|
inclusion: { in: Rolify.resource_types },
|
|
allow_nil: true
|
|
|
|
validates :name,
|
|
inclusion: { in: ROLES }
|
|
|
|
scopify
|
|
|
|
# Returns a somewhat friendly name for the resource related to a given role.
|
|
# In the case of Tag Moderators, a resource_type is not present, so we use the
|
|
# resource_id to grab the specific Tag related to that moderator's role.
|
|
def resource_name
|
|
return resource_type unless resource_id
|
|
|
|
Tag.find(resource_id).name
|
|
end
|
|
end
|