Classifying types of features #3496
Labels
idle 🐌
Issues and pull requests with no recent activity
question ❔
Issues where a question or problem is stated and a discussion is held to gather opinions.
schema ⚙️
Isses or pull requests regarding the JSON schema files used in this project.
In #3420 @jpmedley says:
Currently, BCD stores features in hierarchies that data consumers can walk down.
"api.SpeechSynthesis" gets you things we've installed under that tree.
Beneath it you can find constructors, properties, methods, events and other types of features for this interface or object (the root tree isn't really classified either, but at least we're hopefully getting rid of mixins there).
In the CSS tree this is similar, you have trees like "css.properties" or "css.at-rules" with the expectation that you'll find web platform features of that kind underneath these trees. This works well, but isn't perfect, so additional data is needed to make the data more machine-readable further down in these trees (see #3366).
I'm opening this issue to discuss how we could classify compat data we have in the api/ folder better so that data consumer can work with them best.
A first idea by Joe is to add a "type" property to a feature branch, so that you can filter features as shown in his code snippet.
The text was updated successfully, but these errors were encountered: