Adjust Member Message Status Common Object and Corresponding Architechture #4

Closed
opened 2020-09-06 10:55:16 +02:00 by mpk · 3 comments
Owner
  • Modify the GroupMessageStatusChange event to carry the whole member message status list instead of individual events for every member.

  • Adapt the architecture on all three modules to replace the member message statuses that differ from the one already existing (or just overriding the whole list but preferably the first option).

* Modify the `GroupMessageStatusChange` event to carry the whole member message status list instead of individual events for every member. * Adapt the architecture on all three modules to replace the member message statuses that differ from the one already existing (or just overriding the whole list but preferably the first option).
mpk added this to the v0.2-beta milestone 2020-09-06 10:55:16 +02:00
mpk added the
bug
server
client
M
labels 2020-09-06 10:55:16 +02:00
mpk self-assigned this 2020-09-06 10:55:16 +02:00
mpk changed title from Adjusting Member Message Status Common Object to Adjust Member Message Status Common Object and Corresponding Architechture 2020-09-06 10:56:50 +02:00
mpk modified the milestone from v0.2-beta to v0.3-beta 2020-09-27 15:47:54 +02:00
delvh removed the
bug
label 2020-09-29 18:47:14 +02:00
delvh added the due date 2020-11-10 2020-10-04 09:21:28 +02:00
Owner

The due date was set by @kske. I would've given you until 1/1/2021.

The due date was set by @kske. I would've given you until 1/1/2021.
delvh modified the due date from 2020-11-10 to 2020-10-11 2020-10-05 20:12:15 +02:00
kske removed the due date 2020-10-11 2020-10-13 07:49:52 +02:00
Owner

I am still unsure as to what we are trying to fix here. Could you elaborate on the second point?

I am still unsure as to what we are trying to fix here. Could you elaborate on the second point?
Owner

Closing due to a lack of explanation and no activity.

Closing due to a lack of explanation and no activity.
kske closed this issue 2020-10-20 17:38:53 +02:00
This repo is archived. You cannot comment on issues.
No description provided.