When utilization data changes, re-set the "verified" attribute to
false. Ensure that the "Verified" button in the UI updates
accordingly.
This necessitated a few changes:
Addressing a long-standing bug with detecting model "dirtiness" (this
depends on a somewhat brittle heuristic)
Explicit avoidance of a previously-existing race condition in the UI
tests
Re-structuring the view components for developer weeks and developer
days. The "developer week" view is now soley responsible for
utilization collections, and the "developer day" view only has
knowledge of a single utilization model at a time. In addition to
facilitating the new functionality, this cleaner separation of
responsibilities is less prone to errors (in the from of UI thrasing)
and hopefully makes the application logic easier to reason about.
tkellen
commented
9 years ago
When utilization data changes, re-set the "verified" attribute to
false. Ensure that the "Verified" button in the UI updates accordingly.This necessitated a few changes: