#572 Measures 1: declarations, values, validation and formats
–
- github
- github/openchronology/timeline-app
- github/openchronology/timeline-app#572
- issue
- state:closed
Part 1 of #570. A timeline declares its measures, and its moments and durations carry their values, with no totals yet. - **Declaration:** `settings.measures`: a name, its type (`mpz` or `mpq`) and its presentation (#2 of #570 fills in the presentation). - **Values:** `metadata.measures` on a moment or duration, as canonical text (`"1250"`, `"3/2"`). No entry means zero, so a zero is never stored. - **Validation:** `validateDocument`, the server and the native store all refuse: - an undeclared measure; - a non-integer value for an `mpz` measure; - text that isn't canonical; - names beyond the character set or count limit; - values beyond the digit limit. - **Formats:** `.ochx`, `.och` SQLite, server conversion, offline HTML and ` ` carry the declaration and values. - **Declaration changes:** - renaming a measure; - widening `mpz` to `mpq`; - narrowing `mpq` to `mpz` only when every value is an integer; - removing a measure, which removes its values. https://github.com/circagraph/timeline-app/issues/572
Related
- #2 Context aware datetime picker
- #570 Measures: typed quantities on moments and durations, totalled in every summary
- #577 Measures: declarations, exact values, validation and formats (#572)
- #580 Measures: totals in the PostgreSQL moment tree and its overviews (#574)
- #584 Keep every setting in time-display saves and after following a save
- #588 Measures: the desktop store validates declarations and values
- Merge pull request #577 from openchronology/feat/572-measure-values
- Measures: declarations, exact values, validation and formats (#572)
- Keep every setting in time-display saves and after following a save
Open #572 Measures 1: declarations, values, validation and formats in the timeline