Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Reorganize existing flows #23

Open
2 tasks
hero101 opened this issue Sep 19, 2024 · 0 comments
Open
2 tasks

Reorganize existing flows #23

hero101 opened this issue Sep 19, 2024 · 0 comments

Comments

@hero101
Copy link
Collaborator

hero101 commented Sep 19, 2024

Description

We adopted an existing implementation by the Excalidraw team as PoC. Over time, we have noticed that it can be improved and simplified. The latest changes made the state sync-able on the server, so more events and flows became obsolete or needed to be changed.
This story is about organizing current events in a more structured way, using more message types.

As a
I want
So that

Acceptance criteria

  • Existing events and flows analyzed to break them down into separate messages
  • Events and flows broken down using the analysis

Additional Context

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant