Closed yinonov closed 3 years ago
Is your feature request related to a problem? Please describe. There's no design for sessions - users enrolments data storage
Describe the solution you'd like There should be design for sessions - users enrolments data storage
Additional context
enrolments
should store document relationships between users & sessions purchased.
its id should concatenate the sessionId with userId. e.g. 1pnInIr2t7HQtCUonuC1_7vwvmIaPA0UHQMJ9ZwNF.
1pnInIr2t7HQtCUonuC1_7vwvmIaPA0UHQMJ9ZwNF
price paid timestamp // should be added on write event trigger on cloud function uid sessionId
Session enrolments triggered in web app should produce the following flow
note: not entirely sure on what end the purchase transaction should be made, client or cloud function. look for also idempotency in firebase.
closes #167
Is your feature request related to a problem? Please describe. There's no design for sessions - users enrolments data storage
Describe the solution you'd like There should be design for sessions - users enrolments data storage
Additional context
enrolments
collection -should store document relationships between users & sessions purchased.
document model
its id should concatenate the sessionId with userId. e.g.
1pnInIr2t7HQtCUonuC1_7vwvmIaPA0UHQMJ9ZwNF
.Session enrolments triggered in web app should produce the following flow
note: not entirely sure on what end the purchase transaction should be made, client or cloud function. look for also idempotency in firebase.