Sorry I'm not sure, because with Patch, I get:

---

_{This comment was created with the J!Tracker Application at issues.joomla.org/tracker/joomla-cms/32864.}

That is because I did not want to change the type of the field at this late stage

Why not renaming also the plugin to subform? Seems weird that the filesystem has a subfields name and all the other references now are subform. Reminds me of the com_finder- smart search paradigm and I always found that very unintuitive...

I can do that but its a bigger change.

I have tested this item ✅ successfully on 22967ae

After thinking about this more, I think 'Subform' may not be the best name either. I'm fine with it, but could be changed.

As 'subform' implies you can create a little form inside a bigger form. But it's the opposite, this field type IS the bigger form, which will contain child fields.

So a few alternative ideas:

• Parent Field
• Nested Fields
• Grouped Fields
• Multi-Fields
• Fields Container
• Fields Collection
• Rabbit Hole (jk :D )
• or something along these lines...

I think Nested Fields may be the one that makes most sense, after all it's exactly what it's doing:
https://en.wikipedia.org/wiki/Nesting_(computing)

nesting is where information is organized in layers, or where objects contain other similar objects.

Just throwing some ideas.

Or Subform is fine too. Doesn't really matter much, as long as it works :D

I have tested this item ✅ successfully on 22967ae

RTC

I think the change in this PR is good, it make it consistent with other field plugins which we are having at the moment. Once this PR is merged, we will try to change the plugin to make it become real Subform.

Thanks for testing and merging