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
To make a coded component more designer-friendly within the UXPin editor, sometimes a Higher-Order (HO) component is created that offers different properties than the base component. For example, a button base component may expect an icon and its properties as JSON while the UXPin version may separate out those icon settings into distinct settings (icon name, size, etc).
When viewing the preview spec mode, a developer will see the JSX for the HO component and not the underlying component. This means they cannot copy and paste the JSX code into their app and expect it to work.
It would be nice if the underlying component JSX could be presented in the preview spec mode.
The text was updated successfully, but these errors were encountered:
To make a coded component more designer-friendly within the UXPin editor, sometimes a Higher-Order (HO) component is created that offers different properties than the base component. For example, a button base component may expect an icon and its properties as JSON while the UXPin version may separate out those icon settings into distinct settings (icon name, size, etc).
When viewing the preview spec mode, a developer will see the JSX for the HO component and not the underlying component. This means they cannot copy and paste the JSX code into their app and expect it to work.
It would be nice if the underlying component JSX could be presented in the preview spec mode.
The text was updated successfully, but these errors were encountered: