Files
sailing-analytics/java/com.sap.sailing.domain.shared.android.test
Axel Uhl e4baf5e416 bug6227: add TimePoint.plusResolution()/minusResolution() and convert resolution-tick call sites
Introduces two convenience methods on TimePoint that step by one resolution
unit rather than a hard-coded millisecond:

  TimePoint plusResolution()  == plus(getResolution())
  TimePoint minusResolution() == minus(getResolution())

They are implemented once in AbstractTimePoint and saturate at EndOfTime /
BeginningOfTime just like plus/minus do. Expressing "the next/previous
representable instant" through getResolution() keeps these sites correct
should a finer-resolution TimePoint ever be introduced, instead of assuming
one-millisecond granularity.

All plus(1)/minus(1) call sites whose receiver is a TimePoint and whose intent
is a single resolution tick were converted to plusResolution()/minusResolution()
across production and tests. Deliberately left unchanged:
  - plus(1)/minus(1) on Duration receivers (not TimePoints)
  - TimePointTest overflow/saturation tests that exercise plus(long)/minus(long)
    with the literal 1 on purpose

Assisted-By: Claude Opus 4.8 (claude-opus-5)
2026-09-22 23:18:13 +02:00
..
…