Choose a guideline for descendant flag data
Nobody has claimed this yet.
- Dominant language
- JSON
- Stars
- 5.8k
- Forks
- 2.6k
- Avg merge
- 1d 21h
- Merged PRs (30d)
- 186
Description
Prompted by #6465 and https://github.com/mdn/browser-compat-data/pull/6433#issuecomment-669900198, we do not have a consistent way of considering flag data for features which are descendants of a feature also behind a flag.
Or, more visually, consider a structure like this:
SomeObjectSomeObject()someMethod()
If SomeObject is behind a flag, should SomeObject() and someMethod() duplicate the flag data of SomeObject? If the data should be duplicated, by what mechanism?
Blocks: #8947
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 issue #6465 and the linked comment on pull request #6433 first to understand the motivation and existing discussion. Define an agreed rule for descendant flag data and its duplication mechanism, with a decision that unblocks issue #8947.
Written by the indexing model from the issue text.
Assessment
- Domain
- content
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100