Remove legacy generator data #6017
Merged
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
ghost
added
the
data:js
|
I'm OK with old, removed features being removed from BCD, but I think we ought to come up with and document a guideline for removing obsoleted (is that word? I hope so) features. There are other features like this and it would be nice to have a consistent, reviewable set of criteria for their removal too. |
|
You're absolutely right about that! I've opened a PR to add such a guideline: #6018 (the removal here meets both of the two criteria, fwiw) |
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.
It's now more than two years after removal. I've moved the content into the archive and removed the compat tables from the pages.
There is no reason to keep this around any more and I think it should disappear from other data consumers. (https://caniuse.com/#search=legacy)