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
In Web Components for React, we're currently exploring the custom-element-manifest for our wrapper generation.
In order to create proper interfaces, we would need an enhancement to the CEM so that the origin of an enum is part of the manifest.
Example:
The following snippet is an excerpt of ui5-button CEM:
Feature Request Description
In Web Components for React, we're currently exploring the
custom-element-manifest
for our wrapper generation.In order to create proper interfaces, we would need an enhancement to the CEM so that the origin of an enum is part of the manifest.
Example:
The following snippet is an excerpt of
ui5-button
CEM:With this information we know that the
design
attribute is of typeButtonDesign
, but we don't know where to import the enum from.Proposed Solution
To solve this issue, the CEM offers a
references
array as part of the type, where a name and a package can be specified: https://github.com/webcomponents/custom-elements-manifest/blob/efaf2fc1ca3dcd93e4f392e5d9c72840813ad5ea/schema.d.ts#L179-L183With the new information, the CEM would now look like this:
Proposed Alternatives
No response
Organization
UI5 Web Components for React
Additional Context
No response
Priority
None
Privacy Policy
The text was updated successfully, but these errors were encountered: