daostack / daostack/common-backend
store fcm tokens list with device id
Open
Priority - C
- Dominant language
- TypeScript
- Stars
- 1
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
we only need the latest fcm token for each device
so ideally store just a list of device id & token for each device
Contributor guide
No contributing guide indexed for this repository
Research direction
No files or tests are named. Start by locating the current FCM token storage and the code that updates or reads it, then trace how a device is identified. Done means each device retains only its latest FCM token, with the relevant behavior verified by the existing test or persistence path.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- firebase, typescript
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100