This message was deleted.
# community-help
s
This message was deleted.
f
They are replaced outright, we give precedence to explicit params (only when they're both present in the search query and the preset)
t
Ok so that's what I gathered from reading the docs. However, that's not what i'm observing. Given a preset P where
filter_by
is
inStock:true
Query 1:
Copy code
preset: P
100 results Query 2:
Copy code
preset: P
filter_by: sale:true
1 result However, if I remove
filter_by
from preset P through the Typesense dashboard and refresh the page: Query 2:
Copy code
preset: P
filter_by: sale:true
3 results - the additional 2 results are sale and out of stock. It looks like the preset's
filter_by
is still active when an explicit param is passed through the query. This works great, but just does not line up with the docs
I did double check that there was no client-side filtering happening I guess that shouldn't make a difference though
j
Hmm that doesn't line up with how presets work. Could you help replicate this behavior using a simple set of curl commands like this: https://gist.github.com/jasonbosco/7c3432713216c378472f13e72246f46b
t
I am busy but will get to this whenever I can