Add a username field to the User model, add a /users/setName endpoint
CrsiX opened this issue · comments
Some time ago, there actually was a username field and a similar endpoint. It was abandoned since it was thought of to be useless, because every application should have a username field in its alias and make use of it. But what if a user wasn't part of an application but needed to mention him? Using User 42
is discouraged. Using the alias of another application is discouraged as well. This can only be solved by a general username field.
When creating a new account (registering), then the username field may either be set equally to the alias field or specifically asked from the user, however the frontend application likes to implement it.
This has already been implemented in the latest version v0.5.3
.