By drunken monkey on
Change record status:
Published (View all published change records)
Project:
Introduced in branch:
8.x-1.x
Introduced in version:
8.x-1.36
Issue links:
Description:
While it was often implicitly assumed that item scores and boosts in the Search API are (as in other search frameworks/engines) always non-negative numbers, it was nowhere explicitly specified or checked.
Going forward, setting an item’s score or boost to a negative value will trigger a deprecation warning. In the 2.0.0 release this will be changed to a RuntimeException or Error.
Similarly, passing a non-numeric value (explicitly forbidden via the doc block already) will now also trigger a deprecation warning.
Impacts:
Module developers