Skip to content

[FEAT] Simplify Message -> Status relationship #137

@nivemaham

Description

@nivemaham

Is your feature request related to a problem? Please describe.
Current implementation has explicit message status event entities per message type.

Describe the solution you'd like
this could be simplified and a general message status can be used in the parent class.

Priority
1 (The sooner, the better since this will avoid migration and reduce code complexity)

Difficulty
10

Additional context

Metadata

Metadata

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions