-
-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
make sure that EitherT MonadError syntax works the old way #2029
Conversation
|
||
import ExtraRegressionSuite._ | ||
|
||
class ExtraRegressionSuite extends CatsSuite { |
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.
Why are we deleting this? 🤔
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.
oops I did a rename but didn't include the renamed file in the git. just pushed. good catch.
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.
LGTM except for that one comment I left below :)
67f5861
to
1a8e545
Compare
Codecov Report
@@ Coverage Diff @@
## master #2029 +/- ##
=======================================
Coverage 95.09% 95.09%
=======================================
Files 301 301
Lines 4953 4953
Branches 125 125
=======================================
Hits 4710 4710
Misses 243 243
Continue to review full report at Codecov.
|
flipped the priority sequence between the two
MonadError
instances forEitherT
so that the syntax goes back to the behavior prior to 1.0-RC1. If user need theMonadError
syntax with theMonadError
instance that deals with the Error type on the innerF
, they would need to create a local implicit instance that takes higher precedence, see theRegressionSuite
for examplefixes #2022