Require/lint `version_added: false` where relevant
Nobody has claimed this yet.
- Dominant language
- JSON
- Stars
- 5.8k
- Forks
- 2.6k
- Avg merge
- 1d 21h
- Merged PRs (30d)
- 186
Description
via https://github.com/mdn/browser-compat-data/issues/27427#issuecomment-3184424942
Some browsers are not represented in some feature entries, while others are presumptively version_added: false (e.g., browsers without any webextensions don't get a key in support instead of version_added: false).
We ought to scope certain browsers to certain trees (e.g., don't allow Node in the html or css trees) and use allowlists in trees that may have a mix of relevant and irrelevant browser scopes (e.g., for Node, allowlist—with with wildcards—certain api subtrees).
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Read the linked browser-compat-data issue and comment first, then locate the existing validation or lint entry point for support trees. Done means the relevant browser scopes are constrained or allowlisted consistently, and the lint rules enforce the required false values without rejecting valid entries.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- json
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100