Closed stephenmeehanuk closed 1 year ago
I don't think adding an optional description to the fieldtype is a good idea. It would work in your simple example, but you might have more complicated layouts with more data than a simple description that wouldn't work that way:
I think the best way to go about this issue is to create a collection or global with the data you need and render that dynamically in your template. That's how I do it.
Thanks for the suggestion. I think for my problem, I might be able to get away with making the description part of the view template. If poss, I'd like to try and keep everything in forms.
Hi,
I'd like to replicate this Tailwind radio layout:
It'd be helpful if there was a way to add an optional description to each key in the options array.