You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Return validation errors, if possible in requested :locale
will not support requests directly from browsers (because of CSRF)
We will only do the minimal version, so we just need to make it available to create roles, as seen in the first example
Important for documentation
Note that a primary e-mail Adress must be unique. So for the intented purpose it might be easier, to just always create a person without using the Primary email-adress (:email) and to just use additional-email addresses.
Give some indication as to where they can get group id and available roles types.
To create a user without a role is not recommended as nobody will find that person, unless specifically looking for that entry, if you have an admin permission, or if you try to add the person somewhere else.
Open questions:
If API consumers want to add the role and update existing user, then we also need to document the following:
update user with additional accounts / phone numbers...
create role
update role
delete role
(delete person is very restricted)
Examples:
** Create Person with additional Email (assumes role type and group id are known) **
#527 is not within the the current clients budget, but their use use cases can already be achieved with the current APIs that rails provides.
However documentation for those is lacking also validations just return empty errors.
So we will do the following:
We will only do the minimal version, so we just need to make it available to create roles, as seen in the first example
Important for documentation
Open questions:
Examples:
** Create Person with additional Email (assumes role type and group id are known) **
** Create Person failed (email already taken) **
The text was updated successfully, but these errors were encountered: