What's the feature you think Backpack should have?
Every time you use a field type, it'd be awesome to know there's a corresponding column type... with the same name and the same definition. At first for it to be more intuitive... but later maybe even to be able to define both in one go.
Have you already implemented a prototype solution, for your own project?
No
Do you see this as a core feature or an add-on?
Core
The question is... does this even make sense? Will it not be even more confusing, to have a column type named checkbox for example... that doesn't actually show a checkbox? Or a column named select2 that doesn't actually show a select2?
Food for thought...
Let's see what the fields are, and how their corresponding columns are named (if a column for that field even exists):
FREE Field
Column
checkbox
šØ boolean & check (but none with the same name)
Feature Request
What's the feature you think Backpack should have?
Every time you use a field type, it'd be awesome to know there's a corresponding column type... with the same name and the same definition. At first for it to be more intuitive... but later maybe even to be able to define both in one go.
Have you already implemented a prototype solution, for your own project?
No
Do you see this as a core feature or an add-on?
Core
The question is... does this even make sense? Will it not be even more confusing, to have a column type named
checkbox
for example... that doesn't actually show a checkbox? Or a column namedselect2
that doesn't actually show aselect2
?Food for thought...
Let's see what the fields are, and how their corresponding columns are named (if a column for that field even exists):