-
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
[lexical] Bug Fix: Flow is missing some variables and functions #6977
Conversation
- EditorThemeClasses - BaseSelection - NodeSelection - RangeSelection
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
size-limit report 📦
|
isBackward(): boolean; | ||
isCollapsed(): boolean; |
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 useful to add this here, when it already declares that BaseSelection is implemented?
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.
If I remove those 2 declarations, npm run ci-check
return this error
Cannot implement BaseSelection [1] with NodeSelection because property isCollapsed is missing in NodeSelection [2] but exists in BaseSelection [1]. [prop-missing]
@@ -530,6 +538,8 @@ declare export class RangeSelection implements BaseSelection { | |||
insertNodes(nodes: Array<LexicalNode>): void; | |||
getCachedNodes(): null | Array<LexicalNode>; | |||
setCachedNodes(nodes: null | Array<LexicalNode>): void; | |||
forwardDeletion(anchor: PointType, anchorNode: ElementNode | TextNode, isBackward: boolean): boolean; | |||
getStartEndPoints(): null | [PointType, PointType]; |
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 also looks to be the same as BaseSelection
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.
Same as the other comment, if I remove those 2 declarations, npm run ci-check
return this error
Cannot implement BaseSelection [1] with RangeSelection because property getStartEndPoints is missing in
RangeSelection [2] but exists in BaseSelection [1]. [prop-missing]
dirty: boolean; | ||
clone(): BaseSelection; |
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.
curious about the use cases outside of meta for these added api
just a nit, rearranging clone to be after dirty would break the unenforced abc sorting for props
other then that lgtm
Description
Some variables and function are missing in flow file.
Here are classes affected:
This is the following of #6866