Use previous state when spec retrieval fails #61
Comments
tidoust
added a commit
that referenced
this issue
Nov 27, 2023
This fixes #1130 by turning the "discontinued" standing into a frozen state: when the last published version of web-specs says that the standing of a spec is "discontinued", the code directly reuses the information from that last published version for that spec. There remained a couple of places in the build script that did not give priority to information specified in `specs.json`. This update also fixes that (and needs it!). If a discontinued spec needs to be revived, the only way to do that will be to make the new standing explicit in `specs.json`. Loading the last published version of web-specs could prove useful for #61 as well, but that's not part of this update.
tidoust
added a commit
that referenced
this issue
Nov 27, 2023
This fixes #1130 by turning the "discontinued" standing into a frozen state: when the last published version of web-specs says that the standing of a spec is "discontinued", the code directly reuses the information from that last published version for that spec. There remained a couple of places in the build script that did not give priority to information specified in `specs.json`. This update also fixes that (and needs it!). If a discontinued spec needs to be revived, the only way to do that will be to make the new standing explicit in `specs.json`. Loading the last published version of web-specs could prove useful for #61 as well, but that's not part of this update.
tidoust
added a commit
that referenced
this issue
Nov 28, 2023
This fixes #1130 by turning the "discontinued" standing into a frozen state: when the last published version of web-specs says that the standing of a spec is "discontinued", the code directly reuses the information from that last published version for that spec. There remained a couple of places in the build script that did not give priority to information specified in `specs.json`. This update also fixes that (and needs it!). If a discontinued spec needs to be revived, the only way to do that will be to make the new standing explicit in `specs.json`. Loading the last published version of web-specs could prove useful for #61 as well, but that's not part of this update.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Currently, when something goes wrong for a spec, e.g. because the spec is temporarily down or has moved to another URL, the data update mechanism crashes and remains stuck as long as the issue has not been fixed.
It would be preferrable to (ideally automatically) file an issue about the problem and e.g. reuse previously known info about the spec in the meantime.
The text was updated successfully, but these errors were encountered: