feat: update event message handling across various entities #2508
Conversation
| int get createdAt; | ||
|
|
||
| // The original event message that was used to create this entity. | ||
| EventMessage? get eventMessage; |
There was a problem hiding this comment.
🤔 Shouldn't there be a direct one-to-one mapping between EventMessage and the entity, both ways? Similar to how toJson and fromJson functions correspond with each other.
There was a problem hiding this comment.
Yes, it is. The idea is to map an entity to an event message without spending resources on mapping using the original event.
There was a problem hiding this comment.
@ice-deimos
There might be corner cases - If the entity was changed over time, EventMessage generated by an old entity will differ with an EventMessage generated by the latest entity. That might lead to cases when
old EventMessage -> Entity -> EventMessage != old EventMessage
Plus it seems Entity -> EventMessage takes significant amount of resources, so when we call it frequently, for example when we write an entity to the db, it brings freezes.
But using original EventMessage has several flaws: it increases the overall memory usage + if entity was changed (with .copyWith for example, toEventMessage can't return the origianal EventMessage).
Description
EventMessageby using originalEventMessageTask ID
Type of Change