Skip to content
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

Merged
merged 12 commits into from
Jan 27, 2019
Merged

Conversation

borysfan
Copy link
Contributor

@borysfan borysfan commented Jan 21, 2019

This PR is for #75:

  • Introduce wrapper (MatcherEnvelope) for hamcrest TypeSafeMatcher
  • Input should inherit from MatcherEnvelope

@0crat
Copy link
Collaborator

0crat commented Jan 21, 2019

Job #87 is now in scope, role is REV

@codecov
Copy link

codecov bot commented Jan 21, 2019

Codecov Report

Merging #87 into master will increase coverage by 1%.
The diff coverage is 100%.

Impacted file tree graph

@@            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
Impacted Files Coverage Δ Complexity Δ
...rg/llorllale/cactoos/matchers/MatcherEnvelope.java 100% <100%> (ø) 5 <5> (?)
...rg/llorllale/cactoos/matchers/InputHasContent.java 100% <100%> (+25%) 7 <6> (+3) ⬆️
...java/org/llorllale/cactoos/matchers/MatcherOf.java 63.63% <0%> (-18.19%) 3% <0%> (-1%)

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 84e2fb9...8dde23a. Read the comment docs.

@0crat
Copy link
Collaborator

0crat commented Jan 21, 2019

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

@fabriciofx
Copy link

@borysfan Please, fix this PR title and the explanation what you did on it.

Copy link

@fabriciofx fabriciofx left a 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.

@borysfan borysfan changed the title 75 #75 MatcherEnvelope for TypeSafeMatcher Jan 22, 2019
Copy link

@fabriciofx fabriciofx left a 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.

@fabriciofx
Copy link

fabriciofx commented Jan 23, 2019

@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.

@fabriciofx
Copy link

@borysfan ping

1 similar comment
@fabriciofx
Copy link

@borysfan ping

@borysfan
Copy link
Contributor Author

@fabriciofx I've resolved all your comments.

@fabriciofx
Copy link

@borysfan This PR seems fine to me. Congratulations!

@fabriciofx
Copy link

@rultor merge

@rultor
Copy link
Collaborator

rultor commented Jan 27, 2019

@rultor merge

@fabriciofx Thanks for your request. @llorllale Please confirm this.

import org.hamcrest.TypeSafeMatcher;

/**
* A wrapper class for {@link TypeSafeMatcher}.
Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@borysfan just "Matcher Envelope"

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@llorllale Changed.

@llorllale
Copy link
Owner

@borysfan left you a minor comment.

Also, please leave a puzzle for refactoring other matchers to extend this envelope.

@borysfan
Copy link
Contributor Author

@llorllale New puzzle has been added.

@llorllale
Copy link
Owner

@rultor merge

@rultor
Copy link
Collaborator

rultor commented Jan 27, 2019

@rultor merge

@llorllale OK, I'll try to merge now. You can check the progress of the merge here

@rultor rultor merged commit 8dde23a into llorllale:master Jan 27, 2019
@rultor
Copy link
Collaborator

rultor commented Jan 27, 2019

@rultor merge

@llorllale Done! FYI, the full log is here (took me 3min)

@victornoel
Copy link
Collaborator

@llorllale @borysfan the puzzle of #20 was removed instead of the one from #75...

@victornoel
Copy link
Collaborator

@llorllale also why is there two people working on #75 (see #79)

@0crat
Copy link
Collaborator

0crat commented Jan 27, 2019

The job #87 is now out of scope

@0crat
Copy link
Collaborator

0crat commented Jan 27, 2019

Order was finished: +15 point(s) just awarded to @fabriciofx/z

@0crat
Copy link
Collaborator

0crat commented Jan 27, 2019

Job gh:llorllale/cactoos-matchers#87 doesn't exist in WBS, can't create order

@0crat
Copy link
Collaborator

0crat commented Jan 27, 2019

Payment to ARC for a closed pull request, as in §28: +10 point(s) just awarded to @llorllale/z

@borysfan
Copy link
Contributor Author

@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.

@0crat
Copy link
Collaborator

0crat commented Jan 28, 2019

Are you speaking to me or about me here; you must always start your message with my name if you want to address it to me, see §1

@victornoel
Copy link
Collaborator

@borysfan yes, I can see that. But you removed the puzzle for #20, not the puzzle for #75, that's incorrect :)

@borysfan
Copy link
Contributor Author

@borysfan yes, I can see that. But you removed the puzzle for #20, not the puzzle for #75, that's incorrect :)

@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?

@victornoel
Copy link
Collaborator

@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 :)

@borysfan
Copy link
Contributor Author

@victornoel Ok. I will do that. But we should also do something with other PR for #75. It might be confusing for other people.

@victornoel
Copy link
Collaborator

@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 :)

@borysfan
Copy link
Contributor Author

@victornoel I created PR which reverts PDD for #20. Issue #75 does not have any PDD in the code.

@victornoel
Copy link
Collaborator

@borysfan indeed, you should ask the person that opened #75 to close it now that it is solved

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants