-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
Port List e2e test to unit tests #5030
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
size-limit report 📦
|
|
||
describe('@lexical/list tests', () => { | ||
let container: HTMLDivElement | null = null; | ||
let reactRoot; |
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.
Not a blocker, but I wonder if we even need react here? I guess list plugin should have registerList
or similar exposed, then there's just less of react-related noise in the code
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.
I thought about this, but the reason I ultimately kept it is because I want to be able to easily compose the plugins, many of which don't expose neat handles in the same way as @lexical/list. Most things in @lexical/react are exposed as react components, and those are the bulk of what I want to test so we can get rid of some e2es
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.
That's very nice! ✨
WIP