Repository navigation
User should have a role, or roles - not both #1280
Description
Activity
This is a good point. I think the key problem is that WP treats it like you only have one role a lot of the time, but obviously supports multiple. The 80% use case is going to be a single role because of this, but we need to support multiple. For the flexibility, we might not be able to optimise for single. 😞
Punted to Beta 4
Exposing
roleson read seems correct, because a user can certainly have multiple roles.However, when it comes to setting it, I feel there it may be a case where you want
role=custom_role mode=appendand alsorole=administrator mode=replaceTo extend the multiple-role idea though once it's wide-spread, you might want to doroles=[ administrator, custom_role ] mode=replaceorroles=[ custom_role, custom_role2 ] mode=append.It's worth noting, that WordPress also support per-user capabilities (outside of roles - and I believe as both a "give this user this cap" and "this user cannot perform this cap") which is even more rarely used. It could be worth saying that if you want to use the advanced capabilities/roles of the capabilities system, you should rely upon a plugin which exposes those details.
We're going to support multiple roles by just changing the key to
roleswhich is an array. This makes it more consistent and works for all use cases, rather than trying to support the "single role" use case.
Currently on the response of a user, we return array of roles they have. However, on update / create, the client passed the
roleargument. We should either decide that users only have on role as far as the API concerned, or they have multiple, and you can specifyroleswhen updating the resource.