-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Allow Blueprint Sections to nest their data under a key #1142
Comments
Or another idea: allow an option to remove styling for a "Group" field. Both ideas could be quite useful for us. |
This would probably be the easiest way to make this happen, since I imagine changing the way sections/tabs save data would be quite a lot of work. Closing in favour of #1137. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
As an alternative to the "Group" field type, it would be nice to be able to allow an entire Blueprint Section / tab to have its own data key.
e.g. You have your standard "Main" Blueprint Section with its fields. These are top-level fields on the entry.
You then make a new Blueprint Section that has this feature enabled called
Stuff
, presumably with the keystuff
.You make a field within that Blueprint Section called
Things
that is accessed like:stuff:things
instead ofthings
.The text was updated successfully, but these errors were encountered: