-
Notifications
You must be signed in to change notification settings - Fork 13
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
Conditions integrate #256
Conditions integrate #256
Conversation
- use match(req) instead of toFunction()(req) - use null Condition instead of isEmpty() function
…-shared into conditions_integrate
Codecov Report
@@ Coverage Diff @@
## master #256 +/- ##
=======================================
Coverage 99.49% 99.49%
=======================================
Files 22 22
Lines 1188 1188
Branches 284 284
=======================================
Hits 1182 1182
Misses 6 6 Continue to review full report at Codecov.
|
@trieloff , I added another commit to the branch to add the breaking change, but now the smoke test fails, although it doesn't seem to be related to |
🎉 This PR is included in version 5.3.1 🎉 The release is available on: Your semantic-release bot 📦🚀 |
# [6.0.0](v5.3.1...v6.0.0) (2020-02-28) ### Documentation * **changelog:** mark 5.3.1 as a breaking change ([b556e6e](b556e6e)), closes [#256](#256) [#253](#253) [#254](#254) ### BREAKING CHANGES * **changelog:** The 5.3.1 release introduces breaking changes for conditions handling. This commit formally acknowledges that.
BREAKING CHANGE: rename toFunction() to match()