Difference between revisions of "Talk:Specification"

From RestAuth
Jump to navigation Jump to search
 
Line 2: Line 2:
  
 
The current status for related entities:
 
The current status for related entities:
* When [[Specification#Create a user|creating a user]], properties and groups '''are''' automatically created.
+
# When [[Specification#Create a user|creating a user]], properties and groups '''are''' automatically created.
* When [[Specification#Create a group|creating a group]], it's initial users '''are not''' automatically created, but '''silently ignored'''.
+
# When [[Specification#Create a group|creating a group]], it's initial users '''are not''' automatically created, but '''silently ignored'''.
* When [[Specification#Set groups of a user|setting the groups of a user]], groups '''are''' automatically created.
+
# When [[Specification#Set groups of a user|setting the groups of a user]], groups '''are''' automatically created.
* When [[Specification#Add a user to a group|adding a user to a group]], the group '''is not''' automatically created.
+
# When [[Specification#Add a user to a group|adding a user to a group]], the group '''is not''' automatically created.
* When [[Specification#Set users of a group|setting the users of a group]], uses that don't exist are '''silently ignored'''
+
# When [[Specification#Set users of a group|setting the users of a group]], uses that don't exist are '''silently ignored'''
* When [[Specification#Add a group to a group|adding a sub-group to a group]], it is an error if either group does not exist.
+
# When [[Specification#Add a group to a group|adding a sub-group to a group]], it is an error if either group does not exist.
* When [[Specification#Set sub-groups of a group|setting the sub-groups of a group]], it is an error if any of the named sub-groups does not exist.
+
# When [[Specification#Set sub-groups of a group|setting the sub-groups of a group]], it is an error if any of the named sub-groups does not exist.
  
 
I am open to suggestions. I think this should be handled in a consistent way. The current status is definitely something that grew historically, we can change it.
 
I am open to suggestions. I think this should be handled in a consistent way. The current status is definitely something that grew historically, we can change it.

Latest revision as of 19:41, 5 February 2015

Handling of related entities in 0.7

The current status for related entities:

  1. When creating a user, properties and groups are automatically created.
  2. When creating a group, it's initial users are not automatically created, but silently ignored.
  3. When setting the groups of a user, groups are automatically created.
  4. When adding a user to a group, the group is not automatically created.
  5. When setting the users of a group, uses that don't exist are silently ignored
  6. When adding a sub-group to a group, it is an error if either group does not exist.
  7. When setting the sub-groups of a group, it is an error if any of the named sub-groups does not exist.

I am open to suggestions. I think this should be handled in a consistent way. The current status is definitely something that grew historically, we can change it.

Note: We could even think of adding an autocreate parameter to let the client decide if groups should be created (I wouldn't allow this for users, though?)

Possible solutions

  • Add an "autocreate" parameter to some or all requests. (if only some: What to do with the others?)
  • Automatically create groups, but never automatically create users.
    • Setting multiple sub-groups would also create groups - like properties. But setting a single sub-group (a different request) that doesn't exist would be an error
User:Mati: I vote for this (possibly add an autocreate parameter for groups).
  • Auto-create everything.
  • Auto-create nothing.