-
Notifications
You must be signed in to change notification settings - Fork 19
[FME-4033] prerequisites evaluator #665
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
[FME-4033] prerequisites evaluator #665
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't see any tests. Please add them.
I have them in the next PR (since in this one the Matcher always returns true) |
There are new tests. This matcher is the only one that the evaluator must know, so I wasn't sure about the best way of linking them and testing it. I would appreciate some feedback on that. |
internal func overridePrerequisitesMatcher(_ factory: @escaping ([Prerequisite]) -> MatcherProtocol) { | ||
prerequisitesMatcherFactory = factory | ||
} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Cool. Maybe I'd put it in an extension if possible but this is a good approach 👍
iOS SDK
What did you accomplish?
New PrerequisitesMatcher. New result label and new step in Evaluator (class cleanup too)
How do we test the changes introduced in this PR?
Extra Notes
Matcher in next PR