Nico Hoffmann ෴.
Nico Hoffmann ෴.
I don’t see how the solution would solve the outlined issue of mixed casing - that would be the same. And with properties you would still have have naming collisions...
Keep in mind that we have both pages section and pages fields (same for Files) that serve very different functionalities. This could get very nasty when avoiding breaking changes.
I think I would stick with having sections and fields, but maybe the Panel could be as smart that if a type called on the section level doesn’t exist as...
Hmm pretty sure that this was once a feature request to be able to manually sort them
@neildaniels To be honest, this sounds to me like a very specific use case with even more implications (if the files field uses a query, probably you would also only...
This is more a feature idea than a bug.
Why not? ```yaml title: Collection columns: … side: width: 1/4 sections: fields_side: type: fields fields: picture: type: files main: width: 2/4 sections: fields_main: type: fields fields: heading: type: text ```
Ok, the structure field part understood. Regarding the markup, I think it’d be pretty much the same whether you have 1 column > 1 field section > 3 fields >...
@lukasbestle Will that be part of the database refactoring?
That sounds like we would force developers ti define a language even when they don’t want to care.