cubicweb: comparison schemas/base.py

equal deleted inserted replaced

-:1169d3154be6
+:7ca53fc72a0a
 ERQLExpression, RRQLExpression)
 from cubicweb.schemas import META_ETYPE_PERMS, META_RTYPE_PERMS
 class CWUser(WorkflowableEntityType):
 """define a CubicWeb user"""
-permissions = {
+__permissions__ = {
 'read':   ('managers', 'users', ERQLExpression('X identity U')),
 'add':    ('managers',),
 'delete': ('managers',),
 'update': ('managers', ERQLExpression('X identity U, NOT U in_group G, G name "guests"'),),
 }
 description=_('email address to use for notification'))
 use_email     = SubjectRelation('EmailAddress', cardinality='*?', composite='subject')
 in_group = SubjectRelation('CWGroup', cardinality='+*',
 constraints=[RQLConstraint('NOT O name "owners"')],
-description=_('groups grant permissions to the user'))
+description=_('groups grant __permissions__ to the user'))
 class EmailAddress(EntityType):
 """an electronic mail address associated to a short alias"""
-permissions = {
+__permissions__ = {
 'read':   ('managers', 'users', 'guests',), # XXX if P use_email X, U has_read_permission P
 'add':    ('managers', 'users',),
 'delete': ('managers', 'owners', ERQLExpression('P use_email X, U has_update_permission P')),
 'update': ('managers', 'owners', ERQLExpression('P use_email X, U has_update_permission P')),
 }
 (such as python-projects@logilab.org and python-projects@lists.logilab.org), set this \
 to indicate which is the preferred form.'))
 class use_email(RelationType):
 """ """
-permissions = {
+__permissions__ = {
 'read':   ('managers', 'users', 'guests',),
 'add':    ('managers', RRQLExpression('U has_update_permission S'),),
 'delete': ('managers', RRQLExpression('U has_update_permission S'),),
 }
 fulltext_container = 'subject'
 class primary_email(RelationType):
 """the prefered email"""
-permissions = use_email.permissions
+__permissions__ = use_email.__permissions__
 class prefered_form(RelationType):
-permissions = {
+__permissions__ = {
 'read':   ('managers', 'users', 'guests',),
-# XXX should have update permissions on both subject and object,
+# XXX should have update __permissions__ on both subject and object,
 #     though by doing this we will probably have no way to add
 #     this relation in the web ui. The easiest way to acheive this
 #     is probably to be able to have "U has_update_permission O" as
 #     RQLConstraint of the relation definition, though this is not yet
 #     possible
 'delete': ('managers', RRQLExpression('U has_update_permission S'),),
 }
 class in_group(RelationType):
 """core relation indicating a user's groups"""
-permissions = META_RTYPE_PERMS
+__permissions__ = META_RTYPE_PERMS
 class owned_by(RelationType):
 """core relation indicating owners of an entity. This relation
 implicitly put the owner into the owners group for the entity
 """
-permissions = {
+__permissions__ = {
 'read':   ('managers', 'users', 'guests'),
 'add':    ('managers', RRQLExpression('S owned_by U'),),
 'delete': ('managers', RRQLExpression('S owned_by U'),),
 }
 # 0..n cardinality for entities created by internal session (no attached user)
 subject = '*'
 object = 'CWUser'
 class created_by(RelationType):
 """core relation indicating the original creator of an entity"""
-permissions = {
+__permissions__ = {
 'read':   ('managers', 'users', 'guests'),
 'add':    ('managers',),
 'delete': ('managers',),
 }
 # 0..1 cardinality for entities created by internal session (no attached user)
 class CWProperty(EntityType):
 """used for cubicweb configuration. Once a property has been created you
 can't change the key.
 """
-permissions = {
+__permissions__ = {
 'read':   ('managers', 'users', 'guests'),
 'add':    ('managers', 'users',),
 'update': ('managers', 'owners',),
 'delete': ('managers', 'owners',),
 }
 class for_user(RelationType):
 """link a property to the user which want this property customization. Unless
 you're a site manager, this relation will be handled automatically.
 """
-permissions = {
+__permissions__ = {
 'read':   ('managers', 'users', 'guests'),
 'add':    ('managers',),
 'delete': ('managers',),
 }
 inlined = True
 class CWPermission(EntityType):
 """entity type that may be used to construct some advanced security configuration
 """
-permissions = META_ETYPE_PERMS
+__permissions__ = META_ETYPE_PERMS
 name = String(required=True, indexed=True, internationalizable=True, maxsize=100,
 description=_('name or identifier of the permission'))
 label = String(required=True, internationalizable=True, maxsize=100,
 description=_('distinct label to distinguate between other permission entity of the same name'))
 # configurable security
 class require_permission(RelationType):
 """link a permission to the entity. This permission should be used in the
 security definition of the entity's type to be useful.
 """
-permissions = {
+__permissions__ = {
 'read':   ('managers', 'users', 'guests'),
 'add':    ('managers',),
 'delete': ('managers',),
 }
 class require_group(RelationType):
 """used to grant a permission to a group"""
-permissions = {
+__permissions__ = {
 'read':   ('managers', 'users', 'guests'),
 'add':    ('managers',),
 'delete': ('managers',),
 }
 http://www.w3.org/TR/owl-ref/#sameAs-def
 NOTE: You'll have to explicitly declare which entity types can have a
 same_as relation
 """
-permissions = {
+__permissions__ = {
 'read':   ('managers', 'users', 'guests',),
 'add':    ('managers', 'users'),
 'delete': ('managers', 'owners'),
 }
 cardinality = '*1'
 The target application is responsible for updating timestamp
 when necessary to invalidate the cache (typically in hooks).
 Also, checkout the AppObject.get_cache() method.
 """
-permissions = {
+__permissions__ = {
 'read':   ('managers', 'users', 'guests'),
 'add':    ('managers',),
 'update': ('managers', 'users',), # XXX
 'delete': ('managers',),
 }
 # "abtract" relation types, not used in cubicweb itself
 class identical_to(RelationType):
 """identical to"""
 symetric = True
-permissions = {
+__permissions__ = {
 'read':   ('managers', 'users', 'guests',),
-# XXX should have update permissions on both subject and object,
+# XXX should have update __permissions__ on both subject and object,
 #     though by doing this we will probably have no way to add
 #     this relation in the web ui. The easiest way to acheive this
 #     is probably to be able to have "U has_update_permission O" as
 #     RQLConstraint of the relation definition, though this is not yet
 #     possible
 }
 class see_also(RelationType):
 """generic relation to link one entity to another"""
 symetric = True
-permissions = {
+__permissions__ = {
 'read':   ('managers', 'users', 'guests',),
 'add':    ('managers', RRQLExpression('U has_update_permission S'),),
 'delete': ('managers', RRQLExpression('U has_update_permission S'),),
 }

branch	reldefsecurity
changeset 3877	7ca53fc72a0a
parent 3277	4fdb165ae3de
child 3890	d7a270f50f54