exists: false acts like exists: true

[JasonBarnabe]

The README documents the query option:

store_id: {exists: true},      # exists

This seems to imply that you could do:

store_id: {exists: false},      # does not exist

However, the code seems to not care at all what value is passed; it always does an "exists" check.

It would be good to support exists: false, and/or raise an error on unexpected values for exists.

Working alternative is to use _not: { store_id: {exists: true} }.

[ankane]

Hi @JasonBarnabe, thanks for reporting. Added a warning for non-true values in the commit above, and will change to an error and add support for exists: false in Searchkick 6.