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
Not sure if this is a bug, or just not supported. But anyways...
Using Visibility with pathxxx like pathUndefined does not seem to work on itemPaths in Iterate. Visibility with pathUndefined="/someItemPath" will always show the content, because the itemPath will be considered undefined.
We have some data we fetch from the server. Sometimes certain data fields are missing, and if they are missing we would like to show a Field to insert the data. If the data is there we show a Value.
Using pathUndefined for this seems perfect, but it's not working for itemPath/within Iterate.
🐛 Bug Report
Not sure if this is a bug, or just not supported. But anyways...
Using
Visibility
withpathxxx
likepathUndefined
does not seem to work onitemPath
s inIterate
.Visibility
withpathUndefined="/someItemPath"
will always show the content, because theitemPath
will be consideredundefined
.We have some data we fetch from the server. Sometimes certain data fields are missing, and if they are missing we would like to show a
Field
to insert the data. If the data is there we show aValue
.Using
pathUndefined
for this seems perfect, but it's not working foritemPath
/withinIterate
.To Reproduce
Steps to reproduce the behavior:
https://codesandbox.io/p/sandbox/itempath-visibility-rgnjyt
Expected behavior
I expect (or would like) it to be possible to use
Visibility
foritemPath
in the exact same way as forpath
.Eufemia Version
10.62.4
The text was updated successfully, but these errors were encountered: