better query filters

[TkDodo]

The query filters have lots of flags, some of them contradicting each other, and it become quite confusing very fast and it also supports invalid combinations. Especially the active and inactive resp. refetchActive and refetchInactive flags are problematic, as outlined in this issue

Proposed solution

Replace the active and inactive booleans with a QueryStatusFilter: 'all' | 'active' | 'inactive'. We already map the booleans internally (see here), but we currently also allow for a 'none' state if both booleans are set to false, which doesn't make any sense - you wouldn't mach any query at all.

[TkDodo]

@donysukardi maybe this would be something for you, given that you've already done the ground work in

• invalidateQueries with refetchActive: false on inactive query refetches it #2271

let me know if you want to work on this :)

[TkDodo]

note: 'none' actually makes sense for refetchActive / refetchInactive on invalidateQueries, because there we default to active and need a possibility to say that we just want to invalidate, but don't want to refetch at all.

[donysukardi]

Wow.. That’s fast @TkDodo! Hahaha.. I wanted to reply you, but I suppose it’s too late now 😂

[TkDodo]

sorry, I was just too eager 😆

maybe you can help me out with the naming. I went with type for the filters object and refetchType instead of refetchActive / refetchInactive. Let me know if you have better ideas :)

[donysukardi]

those are perfect already! 👍 great work @TkDodo!