Expose content block sub fields as separate fields towards Craft Controllers/APIs

[KevinBodi]

I like the content block field for things such as reusing fieldsets and especially if they have conditional rules.

A persistent issue with the Content Block field type is its lack of compability with other functionalities, such as:

• Craft Entry Type (Card attributes, Thumbnail Source)
• Craft Element (Field Conditions)
• Craft Entry Table (Columns, Filters)
• FeedMe (Entry identificators, Custom field mapping)
• SeoMatic (Meta field sources) [supported in 5.1.17]

I think that Craft should provide methods or functionality so that other features or plugins will work with Content Block sub fields and perhaps could opt-out or opt-in of displaying sub fields.

[thupsi]

You can use generated fields to kinda get around some of the mentioned limitations. And it would help some more if #17507 is implemented. (Pretty please? 🙂)

Though, the "content block" field being partly a convenience feature, having to do workarounds does take back some of that convenience.