-
Notifications
You must be signed in to change notification settings - Fork 426
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
feat: implementation for events in history #7569
base: next
Are you sure you want to change the base?
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
1 Skipped Deployment
|
No changes to documentation |
1e5303d
to
b97e5ae
Compare
Component Testing Report Updated Oct 23, 2024 9:53 AM (UTC) ✅ All Tests Passed -- expand for details
|
export interface EditDocumentVersionEvent extends BaseEvent { | ||
type: 'document.editVersion' | ||
|
||
releaseId?: string | ||
versionId: string | ||
versionRevisionId: string | ||
mergedEvents?: EditDocumentVersionEvent[] | ||
} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is a new event not mentioned in the initial document.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It won't be part of the events api
⚡️ Editor Performance ReportUpdated Wed, 23 Oct 2024 09:55:59 GMT
Detailed information🏠 Reference resultThe performance result of
🧪 Experiment resultThe performance result of this branch
📚 Glossary
|
2841ec0
to
f638790
Compare
fcf36e3
to
ae3076f
Compare
ae3076f
to
49d773c
Compare
Warning
Not to be merged yet, this requires approval from the CLDX team on how the events are generated.
Description
What to review
This Pr updates how the chunks are defined, using event based actions. This events in a close future will include also the versions.
Eventually, we will have an events API to get them from, so all the mapping won't need to happen in the client.
To create the necessary events we are using the transactions.
Are this changes correct? Are there any missing pieces?
Testing
Open any document and see the history, it should work as always, no visual or functional changes introduced, this is preparing to use the events api.
Tests have been added for the get events functions.
Also, a story has been created showing how the transactions -> events -> chunks logic work.
Notes for release
feat: introduces event based history.