Transferrable subfeatures should have an underscore
Nobody has claimed this yet.
- Dominant language
- JSON
- Stars
- 5.8k
- Forks
- 2.6k
- Avg merge
- 1d 21h
- Merged PRs (30d)
- 186
Description
https://github.com/mdn/browser-compat-data/pull/16281 and https://github.com/mdn/browser-compat-data/pull/16525 added subfeatures for whether objects are transferrable, but can't be distinguished from features that would mean the presence of a transferrable property or method.
Not sure what a good name and description would be at this point, so filing this issue.
cc @sideshowbarker @hamishwillee @queengooborg
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
Start by reviewing the linked pull requests and the existing transferrable subfeatures in the browser-compat-data repository. Determine a naming and description convention that distinguishes transferability subfeatures from a transferrable property or method; done means the proposed names and descriptions are agreed and applied consistently.
Written by the indexing model from the issue text.
Assessment
- Domain
- data
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100