| commit | ff320964b30e3999cfba63bff042197ceba41206 | [log] [tgz] |
|---|---|---|
| author | Ben Rohlfs <brohlfs@google.com> | Thu Oct 29 18:17:10 2020 +0100 |
| committer | Ben Rohlfs <brohlfs@google.com> | Mon Nov 09 09:20:49 2020 +0000 |
| tree | c4a52c200001993e3a31dfdff0e5646c26256ab5 | |
| parent | 4277d78e210c7cd98c29e2403c4cf63ca7a60fe6 [diff] |
Iterate on the data model of checks Most importantly break up Check into CheckRun and CheckResult. While creating wireframes and mocks we have realized that we want to treat runs and results in a substantially different manner, so it felt increasingly artificial to try and model them with the same entity. We had already clearly separated checks into 6 categories, 3 of which were run related and 3 were result related. So breaking this up does not change that much, but makes the two different entities a bit clearer, e.g. by removing `tags` from runs and only allowing one link per run, and by removing the timestamp attributes from results. Change-Id: Id60f7c2abcdf0304d9799cf9e6435b19f4372976
Homepage for Gerrit Code Review.
Instructions how to publish the Gerrit documentation can be found at: https://www.gerritcodereview.com/publishing.html