Documentation vs. code: Clarify and/or fix logic of "filter" function about mqttwarn HOT 3 OPEN

mqttwarn's documentation would match Python's filter function ¹:

filter(function, iterable): Construct an iterator from those elements of iterable for which function is true.

However, mqttwarn's implementation is apparently doing it the other way round, contrary to its documentation. Is it a bug? How would we approach fixing this?

from mqttwarn.

I also stumbled about this. I would suggest to keep the implementation as it is (to not break implementation done by all the users), but update the documentation to be more precise on how to create the filter.

E.g.:

A function called from the filter property in a topic section needs to return True to stop the outbound notification

from mqttwarn.

Documentation fixed with 288392f. Thanks.

from mqttwarn.