Shimmy
Shimmy
> * Should it be generic `HaveElementWithValue(string expectedElement, T expectedValue)`? I like this. > Json is text only, so why don't we stick to a string and a Jtoken overload?...
IMO sky is the limit of where we can go with it. Why not have the `Error` extended to include validation errors or connectivity errors.
I encounter this over and over. I don't like the pragma style which makes me feel like a C++ developer when I'm supposed to write C#. Attributes are scope based,...
Will this be in .NET Core 3.1?
> PostgreSQL has its own hierarchical type - ltree - which is supported by by the PostgreSQL EF provider Hi @roji I'm not sure if that implies there's similar support...
Please add support for interface default implementation, not just `sealed` members. For example: ```csharp public interface IInterface { int Value { get; } string FormattedValue => Value.ToString(); } var mock...
In my scenario, I'm using non-strict mocks. I just want to use the sequence in the verification stage, so that the calls to the various underlying services were made by...
Otherwise, `VerifyInSequence` instead of `Verify`, something like: ```c# [Fact] public void Test1() { // arrange var jobServiceMock = new Mock(); var workServiceMock = new Mock(); using var sequence = Sequence.Create(jobServiceMock,...
> I'm personally gravitating to the first of the two designs just mentioned I'm not sure which one you're referring to.