Represent parent/child class relationship in IDL somehow.
Open
@queengooborg is already working on this.
Since May 14, 2022.
schema
- Dominant language
- JSON
- Stars
- 5.8k
- Forks
- 2.6k
- Avg merge
- 1d 21h
- Merged PRs (30d)
- 186
Description
We currently have a few base classes that are not instantiable. Examples include BaseAudioContext and Sensor, and it's probable that we will have more in the future. This introduces a number of problems:
- Linter rules that are valid for other interfaces can produce false errors.
- Displays of data from the child interfaces are missing items on the parent.
Perhaps the relationship should be captured somehow in the BCD itself. Not only would this provide a consistent and valid hook for alternate linting behavior, it would also allow consumers of the data to show information about parent classes.
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.
Assessment
This issue has not been assessed yet.