filter.Expresson.find() does not handle 'None' values correctly

[code-inflation]

find() doesn't seem to be able to handle None values.

Example:

from jsonpath_ng.ext.parser import parse

data = [{"test": True}, {"test": None}]

query = $[?(test == true)]
parser = parse(query)
parser.find(data)

Causes the following error:

TypeError: int() argument must be a string, a bytes-like object or a real number, not 'NoneType'

[amittendulkar]

Minor correction above. Instead of ,
query = $[?(test == true)]
should be,
query = '$[?(test == true)]'

[Dggz]

Is there any chance this will be fixed? Or is there a chance that PRs addressing this will be merged and released? Is this library still maintained at all?

This part of the code is at least part of the issue since True/False are instances of int, that whole conditional block is broken and it works for actual booleans by chance.

https://github.com/h2non/jsonpath-ng/blame/8a62341c1ad94b7c23427a96dd6ea81367d537b7/jsonpath_ng/ext/filter.py#L107

[denisfrm]

Hi guys!

I made an adjustment to this PR #189 by removing the conditional for boolean values ​​because I didn't find any scenario that requires conversion to bool.
It is possible to convert the boolean to int and trap the TypError. It would work. But I really don't see the need for this condition. Like this:

        for data in datum:
            value = data.value
            if type(self.value) is int:
                try:
                    value = int(value)
                except ValueError:
                    continue
            if isinstance(self.value, bool):
                try:
                    value = int(value)
                except (ValueError, TypeError):
                    continue

The int type in Python can be represented by an integer (0, 1), bool is a subclass of int. So to only handle integers, I changed the isinstance condition to type. This way it rejects subclasses.

If anyone finds a scenario that requires conversion to bool, I can add it to the unit test.