Closed Bug 1274168 Opened 9 years ago Closed 9 years ago

Store participant data in firebase

Categories

(Hello (Loop) :: Client, defect, P1)

defect

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: Mardak, Assigned: Mardak)

References

Details

(Whiteboard: [akita-alpha])

Attachments

(1 file)

We'll need a new participant type and DataDriver interface.
This includes detecting participants and sending out appropriate actions for the store per bug 1274137.
Blocks: 1274181
Rank: 4
Priority: -- → P1
Assignee: nobody → edilee
Blocks: 1274171
Whiteboard: [akita] → [akita-alpha]
Attachment #8757018 - Flags: review?(dmose)
Unclear if the UpdatedParticipant action should actually just have all the fields of the participant, e.g., name at the top level instead of a nested object for participant. This would also mean the data driver wil need to inject the userId into the top level similar to what it currently does by injecting receivedTimestamp.
I updated the PR to have the explicit fields in the action instead of the opaque Object to better match existing actions. mancas, this means you'll need to update the action to have the desired fields that you actually want for bug 1274137.
Comment on attachment 8757018 [details] [review] [loop] Mardak:bug-1274168-firebase-participant > mozilla:akita Thanks for the quick patch! r=dmose, with the comments in the PR addressed.
Attachment #8757018 - Flags: review?(dmose) → review+
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
Blocks: 1276095
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: