Limitations and Known Issues

This article lists current limitations and known issues for Editor React components. Fixes for these issues are in progress.

Manifest limitations

After you create the manifest for the first time, certain changes to existing definitions are considered breaking changes. Breaking changes are blocked by validation and can't be deployed.

The following type fields are immutable once set:

• dataType: The type of a data item.
• elementType: The type of an element.
• cssPropertyType: The type of a CSS custom property.
• refElement.type: The type of a ref element.

Changing any of these fields from their originally saved value results in an error. To use a different type, add a new variable with the desired name and type instead of modifying the existing one.

Additionally, the following structural issues result in validation errors:

• A required type field is undefined.
• A data item with dataType: "data" is missing its data field or has an empty items map.
• A data item with dataType: "arrayItems" is missing its arrayItems field or doesn't define data, dataItem, or dynamicItems.

Unsupported features

The following features are not currently supported for Editor React Components:

• Translations: Some manifest fields, such as displayName in data items, presets, and actions, as well as the top-level resources field, support translations. However, the translation mechanism isn't yet available.
• Custom panels: Building custom editor panels isn't currently supported. The editor generates panels automatically from your manifest's data and style definitions.
• Self-hosting: Self-hosting for editor React component extensions isn't yet supported. Deploy components using the CLI.
• Ref elements: The refElement element type, which lets you reference and reuse existing Wix components with optional overrides, isn't yet supported. Only inlineElement is available.