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
Is your feature request related to a problem? Please describe.
The i18n keys are currently definable within UI Schema options. This doesn't make much sense as merging in a default config with an i18n key is rarely a desired use case.
Describe the solution you'd like
The i18n key should be placed at the root level of the respective UI Schema element.
Describe alternatives you've considered
None
Framework
Core
RendererSet
Other (please specify in the Additional context field)
Additional context
No response
The text was updated successfully, but these errors were encountered:
* The i18n base key can no longer be specified as part of the UI Schema `options`
* Add optional `i18n` property to `ControlElement`
* Adapt i18n key resolution
* Add explicit tests for i18n key extraction from UI Schema and Json Schema
Fixeclipsesource#1942
* The i18n base key can no longer be specified as part of the UI Schema `options`
* Add optional `i18n` property to `ControlElement`
* Adapt i18n key resolution
* Add explicit tests for i18n key extraction from UI Schema and Json Schema
Fixeclipsesource#1942
Is your feature request related to a problem? Please describe.
The
i18n
keys are currently definable within UI Schema options. This doesn't make much sense as merging in a defaultconfig
with ani18n
key is rarely a desired use case.Describe the solution you'd like
The
i18n
key should be placed at the root level of the respective UI Schema element.Describe alternatives you've considered
None
Framework
Core
RendererSet
Other (please specify in the Additional context field)
Additional context
No response
The text was updated successfully, but these errors were encountered: