tree be070990cb171eaf9d8fa77e3cfca328ba0f7f51
parent fddc9d14c830761f6123d936e22f4b9b94b98510
author Ben Rohlfs <brohlfs@google.com> 1673337660 +0100
committer Ben Rohlfs <brohlfs@google.com> 1673361967 +0100

Derive patchRange directly from diff view model

Use `patchNum` and `basePatchNum` directly instead of using a
`patchRange` wrapper.

Remove `initPatchRange()` method. Subscribe to view model instead.

The goal is to pick apart the `viewStateChanged()` method one by one.
Relying on that method to initialize and update correctly has proven
to be extremely error prone. Each piece of data should have a more
direct way of how it is initialized or updated.

The patchset range is maintained by the view model already. Let's
just subscribe to it.

Release-Notes: skip
Change-Id: I21ddf5ce22f6d233bcaf5504c42d236a2812e24a