The process is to wait until the sole maintainer has time to look at it.
This is an open source project and I know people contribute on their free time which is hard to get these days. I was wondering if the maintainer has considered pulling in long term contributors to help out with the PR merges. This would enable faster resolution of issues.
I don't know, but it's a question I asked in one of the issues. Maybe it's worth starting a discussion issue about it?
@JosephWoodward@JakeGinnivan seems shouldly supports some really old dotnet versions. eg 4.5.1 was released 10/2013 and support ended in 2016. just wondering is you have considered dropping some of those in v4?
hi all, anyone experience where Shouldly suddenly doesnt know how to find a diff tool. It's been working perfectly fine in visual studio, then suddenly stops working for no visible reason? the tests still work, as in they verify or fail, just doesnt launch the default visual studio diff tool anymore.
Hi all. I have a little fix for FindMethodUsingAttribute which allows it to correctly discover async test methods. How do I go about getting permission to push the branch and submit a PR?
Hello, So i'm looking at a test method called "ShouldBeSameAs" for comparing objects, however i can't find any documentation on this anywhere? anyone able to assist?
@benjaminroesdal ShouldBeSameAs compares whether two references point to the same object instance. It's a ReferenceEquals test.
Hi there, is the TypeInitializationException in v4 with ShouldMatchApproved a known issue? About to raise a GH issue for it :)
Hi - im using the lates version 4.0.3 i have IEquatable<class> implemented when i test i use expectedValue.ShouldBe(actualValue) i know that thay dont match becuse thay have diffrent values but shouldly wont output any of that information. Do anyone know way ?
or wont it list out the actual diffs of property values ? now it only shows the hashcode
seams to work better when u go directly on the properties, would be nice if it worked directly on the object tho but now i get more info at least
That's more the way ShouldBeEquivalentTo would work. Shouldly doesn’t know which properties are relevent to the IEquatable implementation.
I assert on properties myself.
Hey all! Why isn't ShouldyCoreExtensions externally visible? It seems to be defined on the Shoudly.dll assembly and is public
whelp, that's because i'm not using the latest version