-
- Downloads

backported "Fix case-sensitive option leaking to string/=" (#40603)

* Fix case-sensitive option leaking to string/= (#40535) Fixes #40383 If a native query parameter is set up with a string widget type that supports a `case-sensitive` option, and that parameter is tied to a dashboard filter that did not support that option, the option was still leaking into the filter as an option where options were not expected. For instance the native query parameter used `string/contains` and the dashboard used `string/=`, the QP would try to build a filter like `[:= field value {:case-sensitive false}]` which is an illegal filter. * Fix moved fn --------- Co-authored-by:Case Nelson <case@metabase.com> Co-authored-by:
Chris Truter <crisptrutski@users.noreply.github.com>
Please register or sign in to comment