Main reason is flexibility. If sometimes you need it and sometimes you dont, allowing it to be embedded could be nice.
A more complete solution would be to allow different entities to have different entity layouts, but that might be trickier. (A setting in the entity view)
FYI, I think using the term âmulti-relation viewâ might be misleading for some people.
I suppose you mean the option for multiple (tabbable) relation views, available for collection fields.
I donât think we use the term âmulti-relationâ except in relation to the polymorphism that Highlight support.
Perhaps, instead of proposing a specific solution, you want to elaborate on a use case that you want to address, since I feel it might be solvable in many different ways.
(I did note your other post, so I guess itâs related, but I canât help but wonder if Danielâs idea is a neat solution)
Edited to ârelation viewsâ. Referring to this: Fibery
Will use this terminology, sorry!
I agree.
The main use case was for per entity customisation. This way you can just show the Rich text field, and the users can embed the Relation Views they need into there. The proper solution would be a toggle to allow different Entity Layout per Entity though. So maybe this is not a great suggestionâŚ