You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
With the upcoming changes to plugin typings in version v1.107.0-beta.1, I noticed the introduction of several new node types: SlideNode, SlideRowNode, SlideGridNode, and InteractiveSlideElementNode, which have been added to the SceneNode type. This has resulted in a significant breaking change in our codebase, as we rely heavily on SceneNode. Currently, we're facing over 500+ errors due to the absence of common properties like x, y, width, and height which are not present on the slide-type nodes.
The situation is further complicated by the children of nodes that utilize SceneNode, making it challenging to simply define a custom type that omits slide nodes.
Would the development team consider separating these types to prevent this breaking changes?
Hey Figma team!
With the upcoming changes to plugin typings in version v1.107.0-beta.1, I noticed the introduction of several new node types: SlideNode, SlideRowNode, SlideGridNode, and InteractiveSlideElementNode, which have been added to the SceneNode type. This has resulted in a significant breaking change in our codebase, as we rely heavily on SceneNode. Currently, we're facing over 500+ errors due to the absence of common properties like x, y, width, and height which are not present on the slide-type nodes.
The situation is further complicated by the children of nodes that utilize SceneNode, making it challenging to simply define a custom type that omits slide nodes.
Would the development team consider separating these types to prevent this breaking changes?
For example:
Thank you for your consideration!
The text was updated successfully, but these errors were encountered: