bug: I've ran into this issue several times. edit state is not synchronized.
reproduction flow:
My partner would have some template open, lets say on hyphotetical revision 4.
I would edit same template from another computer, I would make several edits and lets say save it on revision 9.
My partner would then come back to her template and make some revision and save it - and her template is saved on revision 5 and we lost all the changes that I made from another computer...
issue is that state is not synchronized, thus editing by multiple people is not possible
proposed solution:
when person opens notifuse - it should subscribe to an SSE stream of all the events thats happening in the system.
Many computers should be able to subscibe to same sse stream.
instead of request /response fetch calls - when editing one should be making fetch requests, but build the UI based on the SSE responses - this way UI updates propagate to many devices and state is synchronized and fit for collaborative editing.
Ive implemented similar system recently at work and works really well.
bug: I've ran into this issue several times. edit state is not synchronized.
reproduction flow:
My partner would have some template open, lets say on hyphotetical revision 4.
I would edit same template from another computer, I would make several edits and lets say save it on revision 9.
My partner would then come back to her template and make some revision and save it - and her template is saved on revision 5 and we lost all the changes that I made from another computer...
issue is that state is not synchronized, thus editing by multiple people is not possible
proposed solution:
when person opens notifuse - it should subscribe to an SSE stream of all the events thats happening in the system.
Many computers should be able to subscibe to same sse stream.
instead of request /response fetch calls - when editing one should be making fetch requests, but build the UI based on the SSE responses - this way UI updates propagate to many devices and state is synchronized and fit for collaborative editing.
Ive implemented similar system recently at work and works really well.