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
An optional but common requirement for list fields is that it should be possible enter other values in addition to the preconfigured ones.
On modelling level this could for example be implemented by introducing another DSL property which references a string field which then contains the actual values.
The UI could look like this:
As soon as Other is selected in the dropdown, the additional text input appears next to it.
This idea is from @gfr and he will look for improving the concept next.
The text was updated successfully, but these errors were encountered:
An optional but common requirement for list fields is that it should be possible enter other values in addition to the preconfigured ones.
On modelling level this could for example be implemented by introducing another DSL property which references a string field which then contains the actual values.
The UI could look like this:
As soon as Other is selected in the dropdown, the additional text input appears next to it.
This idea is from @gfr and he will look for improving the concept next.
The text was updated successfully, but these errors were encountered: