An idea that originated from here: #1569970: Reuse of field collection entity type on more than one collection field?.

How hard would it be to allow a field collection to become a custom field type?

Since it is basically this now, a content structure comprised of existing fields; would it not make sense if we could edit the FC and select a checkbox that states the collection should create a new custom field type. Then when adding fields to a bundle; this new structure would show in the Field Type select list.

The end result of all of this of course would allow for multiple fields on a bundle to use the same f collection (which currently they can't do).

Comments

willhowlett’s picture

willhowlett CreditAttribution: willhowlett commented

This would be a very useful feature

jmuzz’s picture

jmuzz CreditAttribution: jmuzz commented
Issue summary: View changes
Status: Active » Closed (works as designed)

I'd say it would be fairly hard because a lot of the functionality is tied to the fields being field collection fields and not different custom fields. #2044309: any way to clone a collection structure would sorta be a pre-requisite for this and seems like it should be sufficient by itself. For more separation between the field collection fields and their bundles I'd recommend the paragraphs module because it has a decoupled architecture for those things.