Skip to content
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

Feature: Chaining Matcher #22

Open
mirodietiker opened this issue Aug 15, 2015 · 0 comments
Open

Feature: Chaining Matcher #22

mirodietiker opened this issue Aug 15, 2015 · 0 comments

Comments

@mirodietiker
Copy link
Member

A matcher offers a simple matching for a specific set.

Previously, there was a global match thing to call all matchers for action.
This leads to trouble in case a matcher is only to be executed for a specific case and makes no sense in a global scope.

A chaining Matcher can be selected as a single matcher and internally operates on all selected matchers.
Also it maintains an order and a strategy if it stops after a first successfull match.. or if it executes all matchers and reorders the results at the end by score...

The rules / fields for matching need to be collected from all called matchers to offer contexts.

A problem is if the matchers then allow multiple contact types. Currently the contact type is the bundle that is always set on the contact template. The contact type newly needs to be optional.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant