Mikel Larreategi

@nileshgulia1 but this error is related to the `@users` endpoint and not to `@userschema` right? I am adding a test with different field types and the user schema information is...

I have checked it and indeed the user serializer does not take into account datetime objects: https://github.com/plone/plone.restapi/blob/master/src/plone/restapi/serializer/user.py#L50

And there is no deserializer of users, the property set is done manually without deserializing the user: https://github.com/plone/plone.restapi/blob/master/src/plone/restapi/services/users/update.py#L104

> The other fields work well, I think we can merge it then and take care of other tasks/bugs in subsequent PRs. Yes I do agree. I have some changes...

@jenkins-plone-org please run jobs

Yeah... during the training we wondered if we could restrict somehow the list of exposed interfaces, or at least set a list of known-good-set of interfaces, and expose just them...

I share your concerns about the public visibility of the interfaces. Nevertheless they are needed, at least to know the navigation contexts when the front-end wants to build the global...

I have had to add the following ones to a Plone 4.3.20 buildout: ``` plone.restapi = 7.3.7 PyJWT = 1.7.1 six = 1.11.0 attrs = 21.2.0 plone.rest = 1.6.2 plone.schema...

In that case I would say that we need to control the user persmissions in the endpoint not to allow unauthorized users to get the relation information, while if we...

@stevepiercy do you want me to provide the missing documentation on this branch or let's merge this and then provide specific PRs with the relevant docs?