-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
[lexical-markdown] Breaking Change: rename 'multilineElement' to 'multiline-element' #6617
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
size-limit report 📦
|
@@ -432,7 +432,7 @@ export function transformersByType(transformers: Array<Transformer>): Readonly<{ | |||
|
|||
return { | |||
element: (byType.element || []) as Array<ElementTransformer>, | |||
multilineElement: (byType.multilineElement || | |||
multilineElement: (byType['multiline-element'] || |
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.
im not sure of the historical reason why kebab case was originally chosen as the type name convention.
im open to switching everything to lowerCamelCase if theres a compelling reason
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 looks fine to me, I don't see a compelling reason to use kebab convention other than backwards compatibility and consistency. We don't export these constants so I think we are kinda stuck with the existing value for text-format.
Description
to be consistent with other types like
text-match
,text-format
Test plan
see automated tests