-
Notifications
You must be signed in to change notification settings - Fork 97
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Improve MeFilter #271
base: master
Are you sure you want to change the base?
Improve MeFilter #271
Conversation
The me_tag option does nothing that couldn't be done with the tags option that works on all Filters. Recommend using tags instead of me_tag in the documentation and drop the custom handle_message. Add some code to make existing rules work as expected. As a side-effect this makes [MeFilter] tags = -something work as expected. It used to do nothing, now it removes the something tag.
Instead of accepting only tags_blacklist just pass everything but me_tags to the super class's init function. This way the message can be overwritten in the config which up to now yields an exception: TypeError: __init__() got an unexpected keyword argument 'message'
Codecov Report
@@ Coverage Diff @@
## master #271 +/- ##
==========================================
- Coverage 40.51% 40.40% -0.11%
==========================================
Files 30 30
Lines 980 980
==========================================
- Hits 397 396 -1
- Misses 583 584 +1
Continue to review full report at Codecov.
|
Hello @ukleinek
Yes actually there was some significant progress on the tests side of the project, I will comment the diff. |
Also ping @aidecoe original author of this filter |
Hi ukleinek. What is the improvement? Or is it just a code refactor? |
Note this is completely untested, so please look deeply before merging :-)