> This PR fixes the implementation of `ControlUtils.reducingChange`, which
> incorrectly computed adjacent removed indices, thus resulting in incorrect
> removal notifications.
>
> Since there were no unit tests for this method, I also added a bunch of tests.
>
> After applying this fix, I can
On Sun, 25 Apr 2021 15:35:58 GMT, mstr2
wrote:
>> This PR fixes the implementation of `ControlUtils.reducingChange`, which
>> incorrectly computed adjacent removed indices, thus resulting in incorrect
>> removal notifications.
>>
>> Since there were no unit tests for this method, I also
> This PR fixes the implementation of `ControlUtils.reducingChange`, which
> incorrectly computed adjacent removed indices, thus resulting in incorrect
> removal notifications.
>
> Since there were no unit tests for this method, I also added a bunch of tests.
>
> After applying this fix, I can
>
> I think a minimal constructor would be a nice first step.
I want to avoid adding more constructors, so factory methods would be my
go-to.
We may can go further from that and create something similar like the
> BorderFactory
A factory class or a builder require a whole new class and
On Sat, 24 Apr 2021 20:55:52 GMT, mstr2
wrote:
>> This PR fixes the implementation of `ControlUtils.reducingChange`, which
>> incorrectly computed adjacent removed indices, thus resulting in incorrect
>> removal notifications.
>>
>> Since there were no unit tests for this method, I also
