Drop access-control from biblio.json, now handled in w3c.json
#830
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
`access-control` was marked as an alias of `fetch`. That's not incorrect, but history-wise, `access-control` is more an alias of `cors`, which got superseded by `fetch`. That history wasn't properly recorded in the W3C database. It now is, so W3C update script is currently stuck because it wants to add an `access-control` entry that targets `cors`, duplicating the entry in `biblio.json`. This update drops the entry from `biblio.json`, so that updates may resume. (The superseding relationship between `cors` and `fetch` is not properly captured yet but that's orthogonal to the problem at hand, see tobie#829).
|
... And the update also adds the entry that the W3C update script would add to |
deniak
approved these changes
Oct 21, 2024
dr-shorthair
pushed a commit
to dr-shorthair/specref
that referenced
this pull request
Nov 29, 2024
…e#830) * Drop `access-control` from biblio.json, now handled in w3c.json `access-control` was marked as an alias of `fetch`. That's not incorrect, but history-wise, `access-control` is more an alias of `cors`, which got superseded by `fetch`. That history wasn't properly recorded in the W3C database. It now is, so W3C update script is currently stuck because it wants to add an `access-control` entry that targets `cors`, duplicating the entry in `biblio.json`. This update drops the entry from `biblio.json`, so that updates may resume. (The superseding relationship between `cors` and `fetch` is not properly captured yet but that's orthogonal to the problem at hand, see tobie#829).
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
access-controlwas marked as an alias offetch. That's not incorrect, but history-wise,access-controlis more an alias ofcors, which got superseded byfetch. That history wasn't properly recorded in the W3C database. It now is, so W3C update script is currently stuck because it wants to add anaccess-controlentry that targetscors, duplicating the entry inbiblio.json. This update drops the entry frombiblio.json, so that updates may resume.(The superseding relationship between
corsandfetchis not properly captured yet but that's orthogonal to the problem at hand, see #829).