Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
when i process events, i need to filter them based on specific event data.
i could use predicates as closures, but that solution is too hard and complex, especially if filters have to be dynamic.
i recommend closures if you really have to filter with some particular criteria, but if you just need to filter evaluating event data, i don't think they are the optimal solution.
that's why i added the capability of specifying an array of filters during event registration.
filters are specified as regular expressions.
here's an example:
i did some test with a couple of events and filters, and it actually seems to work.
let me know what you think, i will write a unit test only if you like this.