Fix incorrect filtering logic

[zprobst]

The filter logic was not awaiting the wrong method. Thus everything was not working correctly in the filters. This creates a test for the core logic of a filter and fixes the noted issue.

[codecov]

Codecov Report

Patch coverage: 100.00% and project coverage change: +0.09% 🎉

Comparison is base (c487e57) 94.38% compared to head (fd5ef96) 94.48%.

Additional details and impacted files

@@            Coverage Diff             @@
##             main      #89      +/-   ##
==========================================
+ Coverage   94.38%   94.48%   +0.09%     
==========================================
  Files         122      122              
  Lines        3117     3117              
==========================================
+ Hits         2942     2945       +3     
+ Misses        175      172       -3     

Flag	Coverage Δ
3.10	94.48% <100.00%> (+0.09%)	⬆️
3.11	94.48% <100.00%> (+0.09%)	⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

Files Changed	Coverage Δ
nodestream/pipeline/filters.py	100.00% <100.00%> (+7.14%)	⬆️

☔ View full report in Codecov by Sentry.

📢 Have feedback on the report? Share it here.

[ccloes]

Looks good... could we also implement a test which tests the "NotImplementedError" part of the logic where the Class is implemented incorrectly? Not sure the value, but just a thought.

[zprobst]

Looks good... could we also implement a test which tests the "NotImplementedError" part of the logic where the Class is implemented incorrectly? Not sure the value, but just a thought.

That's not a bad idea. I'll create a follow up PR.