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
The dist/custom-elements.json does not have a "attributes": [] section on any component.
This information is needed to know if an attribute can be set declaratively via HTML and must not be set via JS.
This causes our linters which checks against the dist/custom-elements.json to trigger an error.
Even the examples in the playground tells us to use the attributes, but the documentation says indirectly that you should use accessibleName via Js. This is very inconvenient.
Affected Component
All documented components with attributes
Expected Behaviour
Everything which can be passed declaratively should be listed in the attributes section of the custom-elements.json, like it was before 1.22.0
As a workaround, it is possible to map every member which is a field of type bool, string or something that results in a string to the attributes section.
Organization
No response
Declaration
I’m not disclosing any internal or sensitive information.
The text was updated successfully, but these errors were encountered:
Bug Description
The
dist/custom-elements.json
does not have a"attributes": []
section on any component.This information is needed to know if an attribute can be set declaratively via HTML and must not be set via JS.
This causes our linters which checks against the
dist/custom-elements.json
to trigger an error.Even the examples in the playground tells us to use the attributes, but the documentation says indirectly that you should use
accessibleName
via Js. This is very inconvenient.Affected Component
All documented components with attributes
Expected Behaviour
Everything which can be passed declaratively should be listed in the attributes section of the custom-elements.json, like it was before 1.22.0
Isolated Example
https://sap.github.io/ui5-webcomponents/playground/?path=/docs/main-button--button-overview
Steps to Reproduce
No response
Log Output, Stack Trace or Screenshots
No response
Priority
Medium
UI5 Web Components Version
1.22.0
Browser
Chrome
Operating System
any
Additional Context
As a workaround, it is possible to map every member which is a field of type bool, string or something that results in a string to the attributes section.
Organization
No response
Declaration
The text was updated successfully, but these errors were encountered: