DateTimeOffset?.Should().BeCloseTo(...)

It would be helpful to have .Should().BeCloseTo(...) available for DateTimeOffset? (nullable).

Currently I’ve had to do:

if (request.PreferredAt == null)
{
    response.PreferredAt.Should().BeNull();
}
else
{
    request.PreferredAt.Should()
        .BeCloseTo(response.PreferredAt.Value, TestConstants.MaxAllowedClockDriftMs);
}

[dennisdoomen]

I did, now I need to convince @jnyrup 😉

[ajeckmans]

I went with a similar approach to @eFse7en, but I always check that either both nearbyTime and subject are null or both are not null, and then just continue with the normal becloseto.

In my use case the nearbytime (expectation) can be null, because I’m comparing lists of graphs against each other. In some of the expected graphs there are nullable datetimeoffsets that should be null, but in other cases not. And AFAIK there is no support for or-conditions like “value.Should().BeNull().Or().Be(1)” in FluentAssertions (though it would be awesome if it was possible in an intuitive way)