You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Backend📡Issues corresponding to the backend/API.FeatureNew feature or requestMediumYou should have some familiarity with our codebase to work on this issue
After a user signs up for the first time in our app, we need a way to keep their settings permanent. The ConnectedUser collection in Firebase already semi-temporarily stores some data related to the user (such as location data, which we don't want to save long term) but is deleted as soon as the user closes the app (ie. signs out).
In order to do this, a UserConfig collection should be made after a new authentication account is created. In Firebase this collection is automatically created once a document under a new collection name has been received from the server. For creating these documents I would model off of pre-existing actions like server/src/actions/createConnectedUser.ts.
Then, endpoints to our REST api can be added to create/delete these documents. Focus only on creation for now as we currently have no method for user deletion. After this is done, this API call can be made from the client side next to the code for creating the firebase authentication account, when the user signs up for the first time.
Contact any tech lead if you need help with this issue.
The text was updated successfully, but these errors were encountered:
h1divp
added
Feature
New feature or request
Backend📡
Issues corresponding to the backend/API.
Medium
You should have some familiarity with our codebase to work on this issue
labels
Sep 8, 2024
Backend📡Issues corresponding to the backend/API.FeatureNew feature or requestMediumYou should have some familiarity with our codebase to work on this issue
Related to #254.
After a user signs up for the first time in our app, we need a way to keep their settings permanent. The ConnectedUser collection in Firebase already semi-temporarily stores some data related to the user (such as location data, which we don't want to save long term) but is deleted as soon as the user closes the app (ie. signs out).
In order to do this, a UserConfig collection should be made after a new authentication account is created. In Firebase this collection is automatically created once a document under a new collection name has been received from the server. For creating these documents I would model off of pre-existing actions like
server/src/actions/createConnectedUser.ts
.Then, endpoints to our REST api can be added to create/delete these documents. Focus only on creation for now as we currently have no method for user deletion. After this is done, this API call can be made from the client side next to the code for creating the firebase authentication account, when the user signs up for the first time.
Contact any tech lead if you need help with this issue.
The text was updated successfully, but these errors were encountered: