material-components / material-components/material-web
Add custom-elements.json for each web components
Nobody has claimed this yet.
- Dominant language
- SCSS
- Stars
- 11.3k
- Forks
- 1.1k
- Avg merge
- 20h 28m
- Merged PRs (30d)
- 13
Description
**I'm submitting a:**
- [ ] bug report
- [x] feature request
**Related code:**
```
{
"version": 1,
"tags": [
{
"label": "mwc-button",
"description": "Buttons allow users to take actions, and make choices, with a single tap",
"attributes": [...],
"properties": [...],
"events": [...],
"slots": [...]
}
]
}
```
**w3c/webcomponents discussion:**
- https://github.com/w3c/webcomponents/issues/776
**Used by**
- [Open-wc catalog](https://github.com/open-wc/catalog)
- [Microsoft VS Code](https://github.com/microsoft/vscode-custom-data/blob/master/samples/webcomponents/web-components.json)
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 linked W3C webcomponents discussion and reviewing the repository's web component definitions. Determine how each component should be represented in custom-elements.json, then verify that every web component has metadata usable by Open-wc catalog and VS Code.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- developer-experience, frontend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100