Closed (fixed)
Project:
Custom Elements
Version:
3.x-dev
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
16 May 2024 at 17:51 UTC
Updated:
31 May 2024 at 19:59 UTC
Jump to comment: Most recent
Comments
Comment #2
roderikComment #4
roderikComment #5
fagocommented, please re-check
Comment #6
roderikDone. I found no looping-over-$field_item->getValue() in the codebase, so needed to check a bit. I am not doing a check for "Primitive" anymore (that I took over from DefaultFieldItemProcessor, but I'm not attached to it. Immediately we also have an extra "options" property in the link.
Comment #7
roderikWent with your suggestion "always only apply the values of the first field-item"; it makes things a lot more simple.
No need for the "force_single_value" option now (which I only needed here; I'll reuse that as needed, later) -- no need to extend the raw formatter.
Comment #9
fagoThx! :-) merged!