Add a script to list unmapped compat keys #3525
Open
Conversation
This file contains hidden or 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
github-actions
bot
added
the
tools and infrastructure
ddbeck
force-pushed
the
unmapped-compat-keys
branch
from
ab576e8 to
f500e98
Compare
ddbeck
force-pushed
the
unmapped-compat-keys
branch
from
f500e98 to
d3a1100
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
This adds a script that shows what BCD keys are unmapped by how long they've shipped (weighted toward keys shipped in more browsers). This is toward the first metric described in #3510 (comment), but also a handy tool for me to find keys to map.
The new script covers similar territory as the
stats.tswith the verbose option, so I deleted the duplication.