[Schema] Promote web-features tags to own field
Nobody has claimed this yet.
- Dominant language
- JSON
- Stars
- 5.8k
- Forks
- 2.6k
- Avg merge
- 1d 21h
- Merged PRs (30d)
- 186
Description
What would you like to see added to BCD?
I'm proposing to replace the web-features:X tag values with a dedicated feature or web_feature field.
Example:
- "tags": [
- "web-features:container-scroll-state-queries"
- ],
+ "feature": "container-scroll-state-queries",
Similarly to spec_url and impl_url, this field should support either a single feature or an array of features, in anticipation of some BCD features becoming part of multiple web features:
- "tags": [
- "web-features:foo",
- "web-features:bar"
- ],
+ "feature": [
+ "foo",
+ "bar"
+ ],
How impactful do you think this enhancement will be?
I believe that this enhancement will make it easier to consume the web-features.
Do you have anything more you want to share?
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
The issue does not name specific files, tests, or entry points. Start by locating the schema definitions and existing web-features:X tag values, then determine the migration and validation scope for a feature field that accepts one or multiple values. Done means the schema and affected data consistently use the new field and consumers can rely on it.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- json
- Domain
- data
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100