Closed (fixed)
Project:
Search API
Version:
8.x-1.x-dev
Component:
Plugins
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
4 Aug 2017 at 12:25 UTC
Updated:
3 Sep 2017 at 16:00 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #2
kfritscheAttached patch to fix this issue.
The "- Any -" value is internal "All", but the config schema states for filter_values: boolean, which overwrites this then to true.
Core is doing the same:
core/modules/views/config/schema/views.filter.schema.yml
Comment #3
kfritscheComment #4
drunken monkeyThanks for reporting this!
Did you already create an issue for Core, too? Otherwise, please create one and, in any case, please link it here. For problems that also exist in Core, I usually try to go in tandem with the solution there, to stay as close to the original code as possible.
I actually see a second issue here: After adding the filter, but before saving the view, re-opening the filter config will actually show "False" as the default. Different problem cause, but same area, so you might want to add that to the Core issue (if there is one).
Comment #5
kfritscheIn my last comment with "Core is doing the same" I meant, it is already doing it like this and search_api should catch up. Thats why I added the part from the views schema from core afterwards.
Comment #7
drunken monkeyAh, OK, I seem to have misunderstood.
In that case, sure, let's do the same. Thanks!
Committed.