Bugfix for filter listing when items is null

[mrbokster]

Fix for listing of filter with items None

{'modifier': 'INCLUDES', 'value': {'depth': 0, 'excluded': [{'id': 813, 'label': 'Animated'}, {'id': 1315, 'label': 'Cock Hero'}, {'id': 496, 'label': 'Movies'}, {'id': 1034, 'label': 'PMV'}, {'id': 1316, 'label': 'Stim'}, {'id': 497, 'label': 'Compilation'}], 'items': None}}

Fix for opening of filters that have no value

      {
        "name": "Stashid missing",
        "object_filter": {
          "stash_id_endpoint": {
            "modifier": "IS_NULL"
          }
        },
        "find_filter": {
          "q": "",
          "page": 1,
          "per_page": 40,
          "sort": "date",
          "direction": "ASC"
        }
      },

[gitgiggety]

First of sorry for modifying your original PR and breaking it once more. (This does show it's important to include the criterion(s) / graphql result in the bug so I'm not making the wrong assumptions about criterions which are broken. So if you notice any other issues please try to include the criterion / graphql result.)

I've added two small comments. If you can make those changes I think it will be fine to merge.

[gitgiggety]

@mrbokster, I made the changes (on your branch), can you check these work for you? I did test they work for me

[mrbokster]

Looks good to me and all works on my end as well. No worries about breaking it, im very thankful you created it to begin with and I like coding but have no experience with Python so was fun to have a look at that as well.

Cheers

[mrbokster]

I cant approve it so just leaving a comment, looks good and works on my end.

[gitgiggety]

Well, apparently I still didn't test properly. These changes broke all other (simple?) is_null filters like "URL is null" or "date is null" etc. So I implemented a separate fix for stash_id_endpoint.

Furthermore the "list" handling only worked when depth was set, and didn't properly handle scenarios where it wasn't set (i.e.: it did work for all variants of "tags", but didn't work for any variant of "performer" anymore). All of this should be fixed on the develop branch now. (Which furthermore fixes an older bug where "created / updated at" containing a time didn't work properly. But that's an "old" issue). So after some confirmation of this working I will make another release.