Open silviot opened 1 year ago
Hey @silviot, this is mostly implemented, but I see a small discrepancy between the implementation and the requirements mentioned here:
The newly created user will have all categories associated with them, so the system should allow them to book any slot (until an admin comes in and assigns categories to restrict what they can book).
Currently the user can't book do anything until they've been assigned a category. Did we agree on that, or do you want it implemented as mentioned in the spec ☝️ ?
Athletes should be able to create an entry for themself without any action required by admins. The flow should be:
customers
collection, and the trigger will in turn assign it a secret key and create an entry in thebookings
collection with the secret key. The user will be redirected to their booking management page at this point.The newly created user will have all categories associated with them, so the system should allow them to book any slot (until an admin comes in and assigns categories to restrict what they can book).
Task breakdown
The initial step is already developed. If a user doesn't exist, they can register and a new auth user will be created. There are still a couple of things we should do update in that regard:
name and surname
field, or make it two fields:name
andsurname
(anybody's input/preference appreciated here)After the user is registered, a modal/slide-over/route for registration should be open (we can probably reuse the UI for CustomerProfileForm) at which point, after all of the required fields are filled, the user will get created in firestore and await admins "approval" (assigning a category) at which point we should probably show some message stating: you haven't been assigned to any category, contact your admin, etc.
UI
CustomerProfileForm
:CustomerProfileForm
, without theisEditing
toggle (it would always betrue
) as that seems to be the quickest solutionCloud function (https):