Improve member leave/rejoin workflow
Currently members are marked as left/rejoined by altering the date left or the active ensembles. This isn't intuitive and also raises the question of what should occur when a user modifies both fields at the same time to be in conflict (e.g. alters date left and adds an ensemble). Currently this is just blocked by the back end. Ideally the leave/rejoin logic should be handled properly as a seperate dialog with specialised UX. These dialogs could also be used in #125.
Other things to consider/do:
- How it should be handled if a user adds a new member who already exists (i.e. email address is the same). Ideally a prompt to merge the information be implemented.
- When a member leaves, we should check for current invoices and offer to delete them if desired.
- When a member is deleted, show the impact of the deletion (removal of performances/invoices). Maybe this should only be allowed if there aren't any of those connecting pieces of information?
Edited by Julian Carrivick