We were incorrectly hardcoding the use of .bind query values when using the ~~ (contains) and !~ (not contains) operators with properties having optional values in Fluent filter() expressions. This appears to be the only place where this was still happening.
We were incorrectly hardcoding the use of
.bind
query values when using the~~
(contains) and!~
(not contains) operators with properties having optional values in Fluentfilter()
expressions. This appears to be the only place where this was still happening.Fixes #579.