Current implementation is ambiguous as to whether something is a model or a proposed schema clients can send. For example, DelegateMotionEvent/Payload is also used in SessionLiveState, but the schema doesn't send an id (and it shouldn't) whereas SessionLiveState uses this as a model for storing submitted motions (but it needs an id for processing, or a reference to the object)
This can be done by creating a models.py file that holds future repository (in-memory, saved data) models and storing these there, enhancing decoupling
I'm also sure other examples exist as well, like with Delegation class
Current implementation is ambiguous as to whether something is a model or a proposed schema clients can send. For example, DelegateMotionEvent/Payload is also used in SessionLiveState, but the schema doesn't send an id (and it shouldn't) whereas SessionLiveState uses this as a model for storing submitted motions (but it needs an id for processing, or a reference to the object)
This can be done by creating a
models.pyfile that holds future repository (in-memory, saved data) models and storing these there, enhancing decouplingI'm also sure other examples exist as well, like with Delegation class