Ernst Greiner 🇪🇺Oh Mann, ich schreibe gerade alles um von FluentAssertions auf Shouldly...
Saï@maxitb @jonsagara another #opensource #dotnet project bites the dust. I get it that #opensourced projects where must be funded and sustainable somehow, but that's a terrible news. #fluentassertions and now #mediatr and #automapper 😔 that's just terrible.
Companies should pay for it, not developers!!!
Companies should pay for it, not developers!!!
robrichhttps://github.com/kmtchl/FluentAssertionsToShoudlyConverter - Convert from #FluentAssertions to #Shouldly. Nice work https://github.com/kmtchl.
If you are "unhappy" with license changes in FluentAssertions since version v8.0, you can force it to stay on v7.x.
.NET (Core), project file:
<code>
<ItemGroup>
<PackageReference Include="FluentAssertions" Version="[7.0,8.0)" />
</ItemGroup>
</code>
.NET Framework, packages.config:
<code>
<packages>
<package id="FluentAssertions" version="7.0.0" allowedVersions="[7,8)" targetFramework="net48" />
</packages>
</code>
Or just use Shouldly in future projects...
hth
bitbonk@xunit @bradwilson Is there a way to assert the completion of a `Task<T>` with a timeout and then when the timeout is not hit assert on the result? Similar how it can be done in #FluentAssertions
`task.Should().CompleteWithinAsync(1.Seconds()).WithResult(expectedResult);`
Simon Cropp
Leszek CiesielskiContributors to the #FluentAssertions library aren't happy either: https://github.com/fluentassertions/fluentassertions/pull/2943#issuecomment-2594782282
FluentAssertions v8.0 will cost $ 130,- per Developer.
Just watched Nicks video...
Stop Using FluentAssertions Now
Oh, so #FluentAssertions is changing the license in the new version 8. It doesn't seem like this is, well, particularly in line with what was there before?
https://github.com/fluentassertions/fluentassertions/pull/2943
@ddoomen I am very grateful for all your private time (and probably nerves) you invested in #FluentAssertions for the last 15 years. Fluent Assertions has served us well for more than a decade and saved us a lot of time. I especially liked, how responsive and helpful you were when we had questions or feature requests on github and social media. I can only imagine how much work this is.
You have all my sympathies in your decision to monetize on this effort.