Add TemporalAccessorAssert

Summary

It seems the TemporalAccessor interface may have it’s corresponding (abstract) assert.

Example

abstract class AbstractTemporalAccessorAssert<
        SELF extends AbstractTemporalAccessor<T, SELF>,
        T extends TemporalAccessor>
    extends AbstractTemporalAssert<SELF, T> {
}

Existing assert classes may be refactored extending this class.

abstract class AbstractLocalDateAssert<SELF extends AbstractLocalDateAssert<SELF>>
    //extends AbstractTemporalAssert<SELF, LocalDate>
    extends AbstractTemporalAccessorAssert<SELF, LocalDate>

TemporalAccessor actual = LocalDateTime.now();
assertThat(actual)
    .hasFieldSatisfying(ChornoField.YEAR, y -> { // get(TemporalField) -> IntConsumer
        assertThat(y).isEqualTo(2022);
    })
    .hasLongFieldSatisfying(ChrooField.WHATEVER, l -> { // getLong(TemporalField) -> LongConsumer
    })
    .isSupported(ChronoField.WHATEVER)
    .hasResultSatisfying(TemporalQuery<R> query, Consumer<? super R> c)
    .hasRangeSatisfying(r -> {
        assertThat(r)...; // ValueRangeAssert?
        assertThat(r.getMaximum()).isEqualTo(...);
    });

[scordio]

This is a terribly misdescribed issue. Sorry @scordio

Nothing to be sorry about, @onacit! We are happy to receive any kind of input especially because it’s hard to predict all the possible ways assertions could be used.

[scordio]

Do you have a concrete use case where you would use a TemporalAccessor variable and the assertions in your example?

I’d expect the average usage of the date/time API is with the types provided by the JDK and you’d get already nicer assertions with those.