Autofill IDL members?
Open
Nobody has claimed this yet.
data:api
- Dominant language
- JSON
- Stars
- 5.8k
- Forks
- 2.6k
- Avg merge
- 1d 21h
- Merged PRs (30d)
- 186
Description
Changes like #13884 and #11518 makes it harder to get a support data from a certain IDL member. In pre-3.0 era it was always api.interfaceName.memberName but now there are many cases that this is not true anymore.
How about autofilling things, for example, in building phase:
- Copy
api.VisualViewport.resize_eventtoapi.VisualViewport.onresize.
Not sure how to treat mixins though.
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 build phase that generates IDL member data and trace how api.VisualViewport.resize_event is represented. Define how aliases such as api.VisualViewport.onresize should be generated, including the unresolved treatment of mixins; done means the behavior is specified and covered for the cited example.
Written by the indexing model from the issue text.
Assessment
- Domain
- build-system, data
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100