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
When adding settings and styles options to a grid data type, you need to maintain a JSON object in a textarea. This is cumbersome and errorprone.
What I would suggest, is to use the UI from Nested Content to handle these things.
Then you could have an "add option" button, and a simple UI for setting label, description, key etc.
You could even have different types for the builtin views (textstring, textarea, radiobuttonlist, mediapicker, etc.) so ie. a prevalues field only were available when needed.
The text was updated successfully, but these errors were encountered:
Thanks for the idea @skttl - after a chat at HQ we concluded that yes, your concern is legitimate and the good news is that we've worked on easily providing any property editor as a grid editor. You can follow (or help) the progress in this branch for "The Grid v2".
When adding settings and styles options to a grid data type, you need to maintain a JSON object in a textarea. This is cumbersome and errorprone.
What I would suggest, is to use the UI from Nested Content to handle these things.
Then you could have an "add option" button, and a simple UI for setting label, description, key etc.
You could even have different types for the builtin views (textstring, textarea, radiobuttonlist, mediapicker, etc.) so ie. a prevalues field only were available when needed.
The text was updated successfully, but these errors were encountered: