Details
Details
Please watch this demo video to show that we were able to get the localID succesfully from the client to db
Diff Detail
Diff Detail
- Repository
- rCOMM Comm
- Lint
No Lint Coverage - Unit
No Test Coverage
Event Timeline
Comment Actions
We also need to increase the next local id when a message is sent, but I guess it is handled later in the stack.
Comment Actions
Checked the rest of the stack and it doesn't seem like incrementing the id is handled. We should extend local-id-reducer to react on appropriate action.
To test this thoroughly, we can use a following scenario:
- Send a reaction request and add a sleep on server side
- Send a text message without a sleep (so that it finishes before reaction response)
- Finish sleeping on server side
This scenario might cause some issues when incrementation isn't performed.
Comment Actions
Checked the rest of the stack and it doesn't seem like incrementing the id is handled. We should extend local-id-reducer to react on appropriate action.
Just added D6123 to the stack which should address these concerns