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
Hi @davewwww , thanks for reporting this issue. I agree that it is unexpected and possibly hard to properly detect in the UI when just undefined is returned.
I think we should either return the i18n key as is or return the key with a prefix. E.g. for an unknown key foo something like: MISSING_I18N:foo. @sdirix what do you think?
I'm not sure. If you have a category without i18n and without a label it will also not render any label. To use the i18n value as a fallback, all the user needs to do is to add it as a label too, e.g.
it says that if you have no label and no i18n, then return undefined. this means that if no label exists but an i18n does, then this check does not apply. so either this check is wrong or the following code ignores the fact that you don't need a label if i18n is set.
Describe the bug
While working on #2270 (review), it was discovered that the translation was not working properly.
In the example https://deploy-preview-2270--jsonforms-examples.netlify.app/vue-vanilla/#categorization the second tab "address" is empty. In uischema there is only an "i18n" key defined and no label.
Expected behavior
the expected behavior is that at least the key "address" will be returned, even if it cannot be translated.
Steps to reproduce the issue
Screenshots
No response
Which Version of JSON Forms are you using?
v3.2.1
Framework
Vue
RendererSet
Vanilla
Additional context
No response
The text was updated successfully, but these errors were encountered: