[lexical-devtools-core] Bug Fix: Allow CustomPrintNodeFn to return undefined#7619
[lexical-devtools-core] Bug Fix: Allow CustomPrintNodeFn to return undefined#7619lilshady merged 1 commit intofacebook:mainfrom achaljhawar:main
Conversation
|
Hi @achaljhawar! Thank you for your pull request and welcome to our community. Action RequiredIn order to merge any pull request (code, docs, etc.), we require contributors to sign our Contributor License Agreement, and we don't seem to have one on file for you. ProcessIn order for us to review and merge your suggested changes, please sign at https://code.facebook.com/cla. If you are contributing on behalf of someone else (eg your employer), the individual CLA may not be sufficient and your employer may need to sign the corporate CLA. Once the CLA is signed, our tooling will perform checks and validations. Afterwards, the pull request will be tagged with If you have received this in error or have any questions, please contact us at cla@meta.com. Thanks! |
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
|
Thank you for signing our Contributor License Agreement. We can now accept your code for this (and any) Meta Open Source project. Thanks! |
Description
CustomPrintNodeFntype is strictly typed to returnstring. This causes a TypeScript error if your provided function returnsundefinedto fall back to the default node printing logic, even though the runtime code handles this scenario.CustomPrintNodeFntype definition to bestring | undefined. This aligns the type with the existing runtime behavior and resolves the TypeScript error.Closes #7612
Test plan
Before
If you provided a
customPrintNodefunction like this, you would encounter a TypeScript error:After
With the updated type definition, the above code will no longer produce a TypeScript error. The type checking will succeed, reflecting the actual supported behavior of the
generateContentfunction inlexical-devtools-core.