policies: clarify the role of ChampPolicy
This commit is contained in:
parent
812aef978d
commit
df13bce0e0
1 changed files with 4 additions and 0 deletions
|
@ -1,4 +1,8 @@
|
||||||
class ChampPolicy < ApplicationPolicy
|
class ChampPolicy < ApplicationPolicy
|
||||||
|
# Scope for WRITING to a champ.
|
||||||
|
#
|
||||||
|
# (If the need for a scope to READ a champ emerges, we can implement another scope
|
||||||
|
# in this file, following this example: https://github.com/varvet/pundit/issues/368#issuecomment-196111115)
|
||||||
class Scope < ApplicationScope
|
class Scope < ApplicationScope
|
||||||
def resolve
|
def resolve
|
||||||
if user.blank?
|
if user.blank?
|
||||||
|
|
Loading…
Reference in a new issue