Skip to content
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

Closed
schwartzmj opened this issue Mar 12, 2024 · 2 comments
Closed

Allow Blueprint Sections to nest their data under a key #1142

schwartzmj opened this issue Mar 12, 2024 · 2 comments

Comments

@schwartzmj
Copy link

schwartzmj commented Mar 12, 2024

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 key stuff.

You make a field within that Blueprint Section called Things that is accessed like: stuff:things instead of things.

@schwartzmj
Copy link
Author

schwartzmj commented Mar 12, 2024

Or another idea: allow an option to remove styling for a "Group" field.

Both ideas could be quite useful for us.

@duncanmcclean
Copy link
Member

Or another idea: allow an option to remove styling for a "Group" field.

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
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants