Introduce a new source to get access to the current "i-th" referenced entity from a field entity reference in the context of component per item field formatter

Thanks for your work on this fix (initially started on Drupal Slack here)

I just tested https://git.drupalcode.org/project/ui_patterns/-/merge_requests/320.diff as a patch, and my fields are properly output into my component now! WOOHOO!

For anyone in the future who may see this issue/doesn't have access to Drupal Slack, the issue was I was unable to output props/slots into a block type-based component that had a Paragraphs/Entity Reference Revisions field on it. I was attempting to create a Social Links component as a block type and each Socal Link was a child Paragraph (with social network, link, relationship, etc. as fields/props). I could use the "Referenced entities" option, but it would only output the first field item's values as the values (props) for all of the field items. This fix, so far, seems to correct that to where each field item has its own distinct values/props. I'll be making several more components setup similarly and test to make sure it continues to work for those!

Mikael,

I am happy Dale finds the new source useful :)

I will do the proper review tomorrow, but I have a question.

Is the combination of "Data from a field + "Field prop: entity" the same as "Reference entity" ?

There is no "Reference entity" source ?

if you mean "Referenced entities", no it's not the same :)

2 feedbacks.

Source label in form: Instead of the confusing "Field prop: entity", some proposals: "Field item: entity", "Referenced entity" (singular)... what else?

Also, after selection, we don't see the selected source, but it will be fixed in its own ticket.

Those 2 sources setup are now equivalent because "Reference entities" now behave like the new source:

        slots:
          title:
            sources:
              -
                source:
                  derivable_context: 'entity_reference:node:article:field_tags:taxonomy_term:tags'
                  'entity_reference:node:article:field_tags:taxonomy_term:tags':
                    value:
                      sources:
                        -
                          source:
                            derivable_context: 'field:taxonomy_term:tags:name'
                            'field:taxonomy_term:tags:name':
                              value:
                                sources:
                                  -
                                    source_id: 'field_property:taxonomy_term:name:value'
                                    _weight: '0'
                          source_id: entity_field
                          _weight: '0'
                source_id: 'entity:field_property:node:field_tags:target_id'
                _weight: '0'
          message:
            sources:
              -
                source:
                  derivable_context: 'entity_reference:node:article:field_tags:taxonomy_term:tags'
                  'entity_reference:node:article:field_tags:taxonomy_term:tags':
                    value:
                      sources:
                        -
                          source:
                            derivable_context: 'field:taxonomy_term:tags:name'
                            'field:taxonomy_term:tags:name':
                              value:
                                sources:
                                  -
                                    source_id: 'field_property:taxonomy_term:name:value'
                                    _weight: '0'
                          source_id: entity_field
                          _weight: '0'
                source_id: entity_reference
                _weight: '0'

Reviewed, but hold until @dalemoore validate it.

Hi @pdureau I'm out on personal leave today but will test first thing tomorrow! Thanks again for your and @just_like_good_vibes work on UI Patterns! It's truly something, should be in Core/Drupal CMS IMO

Thanks for the kind words.

It's truly something, should be in Core/Drupal CMS IMO

You may be interested by ✨ Adopt UI Patterns 2 to prepare developers and users for Experience Builder Active

@pdureau Indeed, following—hopefully we will see it included in some way!

I've tested the updated MR as a patch and don't see a noticeable difference, so if I'm not supposed to, I think it's good.