-
Notifications
You must be signed in to change notification settings - Fork 21
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
#75 MatcherEnvelope for TypeSafeMatcher #87
Conversation
Job #87 is now in scope, role is |
Codecov Report
@@ Coverage Diff @@
## master #87 +/- ##
=========================================
+ Coverage 91.73% 92.74% +1%
- Complexity 82 89 +7
=========================================
Files 20 21 +1
Lines 230 248 +18
Branches 3 3
=========================================
+ Hits 211 230 +19
+ Misses 17 16 -1
Partials 2 2
Continue to review full report at Codecov.
|
This pull request #87 is assigned to @fabriciofx/z, here is why; the budget is 15 minutes, see §4; please, read §27 and when you decide to accept the changes, inform @llorllale/z (the architect) right in this ticket; if you decide that this PR should not be accepted ever, also inform the architect; this blog post will help you understand what is expected from a code reviewer; there will be no monetary reward for this job |
@borysfan Please, fix this PR title and the explanation what you did on it. |
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.
@borysfan Done. Please, check out.
src/main/java/org/llorllale/cactoos/matchers/InputHasContent.java
Outdated
Show resolved
Hide resolved
src/main/java/org/llorllale/cactoos/matchers/InputHasContent.java
Outdated
Show resolved
Hide resolved
src/main/java/org/llorllale/cactoos/matchers/InputHasContent.java
Outdated
Show resolved
Hide resolved
src/main/java/org/llorllale/cactoos/matchers/MatcherEnvelope.java
Outdated
Show resolved
Hide resolved
src/main/java/org/llorllale/cactoos/matchers/MatcherEnvelope.java
Outdated
Show resolved
Hide resolved
src/main/java/org/llorllale/cactoos/matchers/ScalarHasValue.java
Outdated
Show resolved
Hide resolved
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.
@borysfan Done. Check out again.
src/main/java/org/llorllale/cactoos/matchers/InputHasContent.java
Outdated
Show resolved
Hide resolved
src/main/java/org/llorllale/cactoos/matchers/InputHasContent.java
Outdated
Show resolved
Hide resolved
src/main/java/org/llorllale/cactoos/matchers/MatcherEnvelope.java
Outdated
Show resolved
Hide resolved
src/test/java/org/llorllale/cactoos/matchers/InputHasContentTest.java
Outdated
Show resolved
Hide resolved
src/test/java/org/llorllale/cactoos/matchers/InputHasContentTest.java
Outdated
Show resolved
Hide resolved
src/test/java/org/llorllale/cactoos/matchers/InputHasContentTest.java
Outdated
Show resolved
Hide resolved
@borysfan Please, change the commit messages. Look at the repo to see the pattern. Sorry, but I won't accept the PR if the commit messages not follow the pattern. And (again): change PR content too. You can see others PR to see the patterns. |
@borysfan ping |
1 similar comment
@borysfan ping |
…adoc. Test case for fail situation
@fabriciofx I've resolved all your comments. |
@borysfan This PR seems fine to me. Congratulations! |
@rultor merge |
@fabriciofx Thanks for your request. @llorllale Please confirm this. |
import org.hamcrest.TypeSafeMatcher; | ||
|
||
/** | ||
* A wrapper class for {@link TypeSafeMatcher}. |
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.
@borysfan just "Matcher Envelope"
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.
@llorllale Changed.
@borysfan left you a minor comment. Also, please leave a puzzle for refactoring other matchers to extend this envelope. |
@llorllale New puzzle has been added. |
@rultor merge |
@llorllale OK, I'll try to merge now. You can check the progress of the merge here |
@llorllale Done! FYI, the full log is here (took me 3min) |
@llorllale @borysfan the puzzle of #20 was removed instead of the one from #75... |
@llorllale also why is there two people working on #75 (see #79) |
The job #87 is now out of scope |
Order was finished: +15 point(s) just awarded to @fabriciofx/z |
Job |
Payment to |
@victornoel Task #75 was assigned to me by @0crat. Please look in the history of #75. I thought that previous work done by @Iprogrammerr was abandoned. |
@victornoel Ohh. Sorry for that. I think I still do not understand the puzzle idea. I am a little bit confused with the numbering. What should we do in this case? |
@borysfan you could create a new PR where you put back the previous puzzle and remove the correct one: like this you will get rewarded for closing #75 as expected and a new puzzle will be created for the previous #20. It a way it's not your fault, ARC and REV should have seen this ;) ARC will decide what to do with your PR anyway :) |
@victornoel Ok. I will do that. But we should also do something with other PR for #75. It might be confusing for other people. |
@borysfan no idea, I think it will resolve by itself, but now as a REV I know I should double-check this kind of things :) |
@victornoel I created PR which reverts PDD for #20. Issue #75 does not have any PDD in the code. |
This PR is for #75: