Rename globals to avoid duplicate BCD keys from a case-insensitive perspective
Open
Nobody has claimed this yet.
data:api
infra
- Dominant language
- JSON
- Stars
- 5.8k
- Forks
- 2.6k
- Avg merge
- 1d 21h
- Merged PRs (30d)
- 186
Description
What type of issue is this?
Other
What information was incorrect, unhelpful, or incomplete?
As discussed in London, it is not ideal that BCD exposes these:
api.crypto <-> api.Crypto
api.performance <-> api.Performance
api.scheduler <-> api.Scheduler
So, we think it would be better to change the global properties to something like api.crypto_property etc.
cc @queengooborg @fiji-flo @claas
What browsers does this problem apply to, if applicable?
No response
What did you expect to see?
No response
Did you test this? If so, how?
No response
Can you link to any release notes, bugs, pull requests, or MDN pages related to this?
No response
Do you have anything more you want to share?
No response
MDN URL
No response
MDN metadata
No response
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
Search the BCD data for the global entries api.crypto, api.performance, and api.scheduler, then inspect how their property names are represented and validated. Done means the affected globals use distinct names such as the proposed *_property forms, with no case-insensitive duplicate keys remaining; the issue provides no file or test path.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- json
- Domain
- data
- Issue type
- Refactor
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100