Internal renaming of elder,leader,regular,basic to numbers

Changed internals so trust levels are referred to with

TrustLevel[1], TrustLevel[2] etc.

This gives us much better flexibility naming trust levels, these names
are meant to be controlled by various communities.
This commit is contained in:
Sam
2014-09-05 15:20:39 +10:00
parent c8d3ffb1ee
commit 59d04c0695
49 changed files with 276 additions and 274 deletions

View File

@@ -22,7 +22,7 @@ class AdminDetailedUserSerializer < AdminUserSerializer
has_one :approved_by, serializer: BasicUserSerializer, embed: :objects
has_one :api_key, serializer: ApiKeySerializer, embed: :objects
has_one :suspended_by, serializer: BasicUserSerializer, embed: :objects
has_one :leader_requirements, serializer: LeaderRequirementsSerializer, embed: :objects
has_one :leader_requirements, serializer: TrustLevel3RequirementsSerializer, embed: :objects
has_many :groups, embed: :object, serializer: BasicGroupSerializer
def can_revoke_admin
@@ -70,7 +70,7 @@ class AdminDetailedUserSerializer < AdminUserSerializer
end
def include_leader_requirements?
object.has_trust_level?(:regular)
object.has_trust_level?(TrustLevel[2])
end
end

View File

@@ -1,4 +1,4 @@
class LeaderRequirementsSerializer < ApplicationSerializer
class TrustLevel3RequirementsSerializer < ApplicationSerializer
attributes :time_period,
:requirements_met,
:days_visited, :min_days_visited,
@@ -13,7 +13,7 @@ class LeaderRequirementsSerializer < ApplicationSerializer
:num_likes_received, :min_likes_received
def time_period
LeaderRequirements::TIME_PERIOD
TrustLevel3Requirements::TIME_PERIOD
end
def requirements_met