How to represent token types/any-value in the schema
Open
Nobody has claimed this yet.
idle
- Dominant language
- JavaScript
- Stars
- 787
- Forks
- 216
- Avg merge
- 1d 5h
- Merged PRs (30d)
- 6
Description
Some of the modern CSS syntax is somewhat hard to define inside our schema. See this conversation:
https://github.com/mdn/data/pull/186
Essentially, we need to decide on a way to represent token types/any-value in the schema, plus any other kinds of types that can't be represented using regular CSS formal syntax.
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 reading the discussion in pull request 186 and the repository's existing schema definitions. Decide how token types, any-value, and other forms that cannot use regular CSS formal syntax should be represented; done means the schema approach is agreed and documented for implementation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- css, json
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100