Extra fields are fake fields used to inject content into the form or display of an entity. It is a Core feature used by many modules and custom implementations.
Currently, extra fields are not available in pattern sources so they cannot be added to pattern fields and rendered within a pattern.
Add a Source plugin to make extra fields available.
| Comment | File | Size | Author |
|---|---|---|---|
| #8 | Capture d’écran de 2022-10-12 18-10-57.png | 39.17 KB | grimreaper |
| #8 | Capture d’écran de 2022-10-12 18-08-43.png | 79.8 KB | grimreaper |
Show commandsStart within a Git clone of the project using the version control instructions.
Or, if you do not have SSH keys set up on git.drupalcode.org:
changes
Comments
Comment #2
duaelfrCode has been pushed to drupal.org fork.
Tests are still to be written.
Comment #3
g4mbiniComment #5
duaelfrThere we go!
Comment #6
grimreaperTo manually test what can be done?
On user entity, the history extra field for example can be injected inside a pattern now?
Something like that?
Comment #7
duaelfrYou can do that yes.
If you use Field Layout or Field Group (with the appropriate UI Patterns submodule), you'll be able to see if you can put the extra field in your pattern and if it's rendered as expected.
Comment #8
grimreaperOk for me.
I have tested with the "member for" field on the user profile and Field Layout, the MR was not needed in this case.
But then I tried with Field group on the basic page content type (see screenshot), and now without the patch the "links" extra field was not detected whereas whit the patch yes.
Merging.
Comment #10
grimreaperComment #13
grimreaperMerged.
And I have added an empty commit for credit to @DuaelFr automated tests.
Thanks everyone!
Comment #15
grimreaperSquash during merge had removed @yannickoo commit authoring...
So another empty commit for him...