Implement password updates via the settings page #103
Notifications
Due Date
No due date set.
Depends on
Reference: lfk/frontend#103
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Or rather implment the settings page...
I think we should do that before letting other people use the system....
Stuff the user should be able to do on the settings page:
The backend already has an endpoint that authenticated users can use to update themselves: /api/users/me