Skip to content
This repository has been archived by the owner on Sep 26, 2023. It is now read-only.

bcd-update: do not spuriously report modifications #2326

Merged
merged 1 commit into from
Sep 14, 2022

Conversation

jugglinmike
Copy link
Contributor

Because the return value of update is used only to optimize I/O, false positives only degrade efficiency--not correctness. However, the underlying behavior substantively effects the interpretation of the "mirror" support value. Due to an unrelated bug (where modifications to mirrored support values are not written back to disk), this error cannot currently be observed.

Correct the return value for this condition in order to improve efficiency and prepare for a later correction to the "mirror" feature.

Because the return value of `update` is used only to optimize I/O, false
positives only degrade efficiency--not correctness. However, the
underlying behavior substantively effects the interpretation of the
`"mirror"` support value. Due to an unrelated bug (where modifications
to mirrored support values are not written back to disk), this error
cannot currently be observed.

Correct the return value for this condition in order to improve
efficiency and prepare for a later correction to the `"mirror"` feature.
@foolip foolip merged commit 6e52a10 into foolip:main Sep 14, 2022
jugglinmike added a commit to bocoup/browser-compat-data that referenced this pull request Sep 28, 2022
These changes were generated procedurally by the mdn-bcd-collector
project using data collected from Chrome for Android and following three
corrections to its interpretation of the "mirror" support value:

foolip/mdn-bcd-collector#2326
foolip/mdn-bcd-collector#2297
foolip/mdn-bcd-collector#2280
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants