Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.Problem/Motivation
With pager:
: [items[0].title] Integer value found, but a string is required/n[items[1].title] Integer value found, but a string is required/n[items[2].title] Integer value found, but a string is required/n[items[3].title] Integer value found, but a string is required in <em class="placeholder">Drupal\Core\Theme\Component\ComponentValidator->validateProps()</em>
Issue fork ui_patterns-3490733
Show commands
Start 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 #3
grimreaperComment #4
just_like_good_vibesthe check seems a bit weak.
what cases we have?
integers, strings, markup, render array ?!, bool, floats, arrays...? who knows
i guess we wan't to keep the normalizing efficient and simple while
protecting against bad data injected, whatever it comes
from.
do we add other cases?
Comment #5
just_like_good_vibesmore generally, do we need a better normalizing for string props? in that case the title of a link maybe normalized the same way string props are/would be normalized ?
Comment #6
pdureau commentedUnfortunately, we cant' apply StringPropType normalization to links item titles, because we discovered than links item titles can be renderables.
Comment #8
pdureau commentedComment #9
just_like_good_vibesaccording to comments from #3491238: [2.0.0-beta6] normalization of slots triggers some unwanted filtering,
there are new work to do on normalization.
i have opened a new separate issue https://www.drupal.org/project/ui_patterns/issues/3492211
Comment #10
pdureau commentedComment #11
pdureau commented