-
-
Notifications
You must be signed in to change notification settings - Fork 395
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
refactor(edgeless): surface elements api #5874
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
1 Ignored Deployment
|
This is almost ready. We can book a meeting to review the code and discuss the technical details tomorrow. @doodlewind |
I have corrected some issues with variable naming:
And add generic type to |
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.
Is it possible to remove legacy code defining fields on previous elements? I would supposed to see more deletions :)
Yes, but I'm not planning to do this in this PR. I'll start a new PR on cleanup and replacement or something once this gets merged. |
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.
Look forward to the housekeeping :)
Move surface elements related API onto the surface model. Introduce a new pure data element model to replace the existing one to make it independent from the renderer. Additionally, this new element model will not depend on the DOM API.