zdm/envoy
zdm
/
envoy
Archived
3
Fork 0
Code Issues 22 Pull Requests Releases 1 Wiki Activity

Adjust Member Message Status Common Object and Corresponding Architechture #4

New Issue
Closed
opened 2020-09-06 10:55:16 +02:00 by mpk · 3 comments
mpk commented 2020-09-06 10:55:16 +02:00
Owner
Copy Link

  • 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
delvh commented 2020-10-04 09:22:40 +02:00
Owner
Copy Link

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
kske commented 2020-10-13 07:50:33 +02:00
Owner
Copy Link

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?
kske commented 2020-10-20 17:38:53 +02:00
Owner
Copy Link

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 Branch/Tag Specified
Branches Tags
develop
f/fancy-diagrams
v0.2-beta
v0.1-beta
Labels
Clear labels   
client

Envoy Client

  
server

Envoy Server

  
user made

This issue has been created through Envoy

  
bug

Something is not working

  
bugfix

Fixes a bug

  
discussion

This has to be discussed

  
documentation

Related to documentation

  
feature

Introduces a new feature

  
L

Branches where 300 < X <= 600 lines are added and more than one work day is needed

  
M

Branches where 100 < X <=300 lines are added

  
maintenance

Related to project maintenance

  
postponed

Won't be done in the immediate future

  
refactoring

Refactoring code or architectures

  
S

Branches where X <= 100 lines are added or less than 30 minutes are needed

  
wontfix

Will not be fixed in this state of development

  
XL

Branch where X > 600 lines are added and more than two work days are needed

No Label
client
server
user made
bug
bugfix
discussion
documentation
feature
L
M
maintenance
postponed
refactoring
S
wontfix
XL
Milestone
Clear milestone
No items
No Milestone
v0.3-beta
Assignees
Clear assignees
No Assignees
mpk
3 Participants
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: zdm/envoy#4
No description provided.
Delete Branch "%!s(<nil>)"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?