-
Notifications
You must be signed in to change notification settings - Fork 652
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
Add infix modifier to collections matchers #404
Comments
Yes good idea. |
I forked master and created a branch with the |
Excellent. Please make a PR and I'll merge. |
I'll include this in 3.1.10 |
@sksamuel When is 3.1.10 due? |
I'll try and do it tonight. I need to branch from master and cherry pick a few commits. |
3.1.10 is released. |
Hitting refresh button at |
You'll be waiting hours for that UI to update.
Once it's in the repo you're good to go
http://repo1.maven.org/maven2/io/kotlintest/kotlintest-assertions/
…On Thu, 13 Sep 2018 at 09:23, Jens ***@***.***> wrote:
Hitting refresh button at
https://search.maven.org/search?q=g:io.kotlintest%20AND%20a:kotlintest-assertions%20AND%20v:3.1.10
😁
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
<#404 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAtZGv20HWBFBdtH3GVu7TEObaj7RPK_ks5uahYAgaJpZM4WlMj7>
.
|
Thanks @sksamuel ! |
This is not applicable to vararg param functions due to limitation in language, but it would look better in for all collections matchers where it is possible.
The text was updated successfully, but these errors were encountered: