Optional namespacing of Tabs fields #776
slavanossar
started this conversation in
Feature Requests & Ideas
Replies: 1 comment 1 reply
-
We love this idea! Thanks! |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I've been playing around with the new
Tabs
field, really nice addition (congrats on v1!). I was previously using theGroup
field to separate lots of fields logical groupings. This also allowed reusing fields in multiple groups on a collection without worrying about name collisions, since all fields within a group were contained within their own object based on the Groupname
.Since the
Tabs
field doesn't do this, I'm currently placing a singleGroup
field within the tab so I can retain the existing field structure.I understand the
Tabs
field is designed to be purely presentational, but it might be useful if tabs also had an optionalname
field that made them function similarly to aGroup
field? It would give more flexibility for how they are used, and eliminate the need for a single redundantGroup
field to namespace the fields within.Beta Was this translation helpful? Give feedback.
All reactions