[2.0.0-alpha2] Field Formatters: Re-enable the source plugin entity reference

Thomas, let's discuss about this issue. I don't understand what needs or be re-enable here.

We expect 3 sources in this scope:

• The one from field label to string prop >> Already implemented
• The one from formatted field (with another field formatter) to slot >> TODO
• The deriver, from each field property to compatible props >> Already implemented

Pierre want it as new settings inside the form...

We need to avoid sources specific to field types, so I don't see which settings I am wanting here :)

Once the source from formatted field (with another field formatter) to slot will be implemented, it can be used with entity reference fields, for example with the "Rendered entity" field formatter.

It'as about what you call "transverse entity" when the field is an entity reference. What we did first is to set field of entity reference directly inside source and you said to us you want it as an new select inside settings.
Maybe we can have new source plugin called "field of entity reference" something like this and have two select to get the field and property of entity reference.

Moved to 2.1.x

let's do a little revival but differently with our new architecture of DerivableContexts.

i take the issue

i think the code may be ready. I just included temporarily some code from 🐛 [2.0.0-beta3] Unable to properly use derivable contexts in a views row style options Active

and finally, a nice working version to review :DDD

Hi @just_like_good_vibes,

it works great. I tested it right now. Works great - but it is hard to review.

We should split into:

- The refactoring of the context filter system.
- The refactoring of views.
- The entity reference

What do you think?

hello,
as i said, the refactoring of views was just copy pasted from another issue :)
i just pushed it here in this temporary MR to be able to fully test the functionality and have some reviews from you :)

Hi guys,

Thanks for working on this feature.

However, can we wait I have created a companion issue before merging ? Maybe we will find some links between both

blocked by 📌 [2.0.0-beta4] Evolution of DeriableContexts : refactor code with source plugin manager, add several contexts in derivation, and better support prop types Active which is in review

just_like_good_vibes → closed merge request !227

ok now that other issues have been created and merged, let the magic of entity reference happens !
i will repush the code, let's go !

I have reworked the code, even better than last time.
please review :)

found a little bug on taxonomy_term

ok christian, let's try it :)

Automatically closed - issue fixed for 2 weeks with no activity.