Problem and Motivation

The widget display is not clear enough on the edit form when there are many fields on a relation type. It would be better to implement a widget which is closer to how the inline entity form handles this aspect.

Possible solution

Create a new widget that shows only the endpoints autocomplete and a render of the related entity in the edit form (just the related field values), and then there would be an edit link to edit the related entity fields (in a popup for example).

The field values should be displayed under the endpoints because the user should be able to check all the values without the need to click on each edit link one by one when searching a value.

Comments

solotandem’s picture

Are you not stating your opinion as fact:

The field values should be displayed under the endpoints because the user should be able to check all the values without the need to click on each edit link one by one when searching a value.

Doesn't the user have the ability to view the relation entities separate from the endpoints? If so, then that is the place to display the details (as with every other entity out there). If not, why not?

Less clutter on the endpoint form is better UI design. You should not be editing the relation fields here so why show all of them.

nagy.balint’s picture

Doesn't the user have the ability to view the relation entities separate from the endpoints?

There is a relation admin UI, however it might be disabled, and its not for the end user. So no you cannot edit these fields without any additional modules, cause relation is just an API.

And this is the exact goal of this module to provide a way to edit the relation from the edit form including the fields contained in the relation.

nagy.balint’s picture

I can suggest the https://www.drupal.org/project/relation_select module in case you do not want to edit the fields contained in the relation on the edit form.

brunodbo’s picture

Can we make this optional (e.g., a checkbox in the field config), so a site builder has the choice to either show all the relation's fields, or use a simple relation add field as it is now?