Change Details

Enter `1.991+-1` in a quantity statement. It is stored via the API as expected (Amount: 1.991, Upper bound: 2.991, Lower bound: 0.991), but rendered as `2+-1`. This causes data-loss when re-editing. Found this while reviewing https://github.com/wmde/WikidataBrowserTests/pull/66.

Enter `1.991+-1` in a quantity statement. It is stored via the API as expected (Amount: 1.991, Upper bound: 2.991, Lower bound: 0.991), but rendered as `2+-1`. This causes significant data loss whenever somebody uses the shown value. Found this while reviewing https://github.com/wmde/WikidataBrowserTests/pull/66. >>! In T95425#1602181, I added: >This was never exclusively about editing. The editing issue was fixed in https://github.com/wmde/ValueView/pull/183/files#diff-6e3ed44714251084b2ff46be5bb6b80fR54, as a side effect while working on T110183. But when copy-pasting a formatted quantity value there is still the same significant data loss involved and the value does not survive (manual) round trips.

Enter `1.991+-1` in a quantity statement. It is stored via the API as expected (Amount: 1.991, Upper bound: 2.991, Lower bound: 0.991), but rendered as `2+-1`. This causes significant data- loss when re-editingever somebody uses the shown value. Found this while reviewing https://github.com/wmde/WikidataBrowserTests/pull/66. >>! In T95425#1602181, I added: >This was never exclusively about editing. The editing issue was fixed in https://github.com/wmde/ValueView/pull/183/files#diff-6e3ed44714251084b2ff46be5bb6b80fR54, as a side effect while working on T110183. But when copy-pasting a formatted quantity value there is still the same significant data loss involved and the value does not survive (manual) round trips.