Refactor IOMatchers to add Generic #707
Merged
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.
Description of changes
We split the IOMatchers trait to make it independent from IO.
RuntimedMatchers
trait, which is generic on the effect typeF[_]
, and has most methods fromIOMatchers
.RuntimedMatchers
defines two methods, that act as placeholders forIO.timeout
andIO.unsafeRunSync
.RunTimedMatchers
trait, we add an innerTimedMatcher
class, that has most of the logic from theIOMatcher
class. This class has methods, akin tocheckIOWithDuration
andcheckIO
, but with different names.Having moved most of the logic to
RuntimedMatchers
, theIOMatcher
becomes just a specific instance ofRunTimedMatchers[IO]
, and the two methods just call the IO methods.IOMatcher
inner class insideIOMatchers
, for compatibility. This class keeps the twocheckIOWithDuration
andcheckIO
methods above.Related tickets
http4s
, which contains a copy ofIOMatchers
.cats.effect.IO
was made and discussed in this issue. Nevertheless, since no appropriate type-class at present, declaring abstract methods inRuntimedMatchers
is the next best.