Skip to content

Conversation

@ishymko
Copy link
Contributor

@ishymko ishymko commented May 6, 2019

Add "satisfy respectively" assertion, similar to xUnit Assert.Collection (#882).

Copy link
Member

@dennisdoomen dennisdoomen left a comment

Choose a reason for hiding this comment

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

Absolutely love this feature!

@dennisdoomen dennisdoomen requested a review from jnyrup May 7, 2019 06:30
Copy link
Member

@jnyrup jnyrup left a comment

Choose a reason for hiding this comment

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

Great implementation 👍

I'm not entirely sure about the name SatisfyRespectively.
From the name, it doesn't immediately strikes me what it's supposed to do.
@dennisdoomen IIRC you have sometimes got valuable feedback from your Twitter network for brainstorming?

@ishymko ishymko force-pushed the issue/882-satisfy-respectively branch 2 times, most recently from 10e43e9 to cc703dc Compare May 7, 2019 08:51
@ishymko
Copy link
Contributor Author

ishymko commented May 7, 2019

Hmm, tests failed two times in a row at AppVeyor, based on the tests failed, I suppose it's related to #1022. @jnyrup @dennisdoomen can I restart build somehow other than pushing new changes? Tests are passing stable on my machine, so fails are most likely not related to my changes.

@ishymko ishymko force-pushed the issue/882-satisfy-respectively branch from cc703dc to 7f7f30b Compare May 11, 2019 07:52
@jnyrup jnyrup merged commit 9c87318 into fluentassertions:master May 15, 2019
@jnyrup
Copy link
Member

jnyrup commented May 15, 2019

@vanashimko Thanks for the contribution to Fluent Assertions.
Look out for your name in the next release.

@ishymko ishymko deleted the issue/882-satisfy-respectively branch May 15, 2019 20:12
@mdilovar
Copy link

mdilovar commented Jun 5, 2019

Which version will this be available in?

@jnyrup
Copy link
Member

jnyrup commented Jun 5, 2019

@mdilovar It will be available in the next release, which will be 5.7.0.
I can't give a release date, but I can assure you that we're also eager to get the next release out.
We're working as I write on weeding out the last issues before being ready to push the release button.

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.

4 participants