Hey there,
Sharing a thought again. The current implementation of the SearchFilter forces to define one but only one specific search strategy for a property among exact, partial, start, end, word_start (and their insensitive variant).
Problem is we cannot have 2 or more of these strategies available for query. Thus it would be, imho, faily easy to achieve that with the same behaviour as the DateFilter.
The implementation could still define a strategy which could be the default strategy to apply.
Example with a SearchFilter configured on a prop named "city" with strategy "exact":
?city=amsterdam
?city[exact]=amsterdam //same effect as previous line
?city[start]=new
?city[end]=york
?city[partial]=ris
etc.
Hey there,
Sharing a thought again. The current implementation of the SearchFilter forces to define one but only one specific search strategy for a property among exact, partial, start, end, word_start (and their insensitive variant).
Problem is we cannot have 2 or more of these strategies available for query. Thus it would be, imho, faily easy to achieve that with the same behaviour as the DateFilter.
The implementation could still define a strategy which could be the default strategy to apply.
Example with a SearchFilter configured on a prop named "city" with strategy "exact":
?city=amsterdam
?city[exact]=amsterdam //same effect as previous line
?city[start]=new
?city[end]=york
?city[partial]=ris
etc.