Add class merging to WebC HTML-only components without use of webc:root="override"
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 1.4k
- Forks
- 46
- Avg merge
- 10m
- Merged PRs (30d)
- 2
Description
Is your feature request related to a problem? Please describe.
With an HTML-only component, using webc:root on an element to enable class merging with the host element effectively turns it into a dynamic component because the host element isn't stripped away. You can fix this by using webc:root="override" but this feels like an extra strep the user shouldn't need to take.
Describe the solution you'd like
If the 11ty logic already knows when something is an HTML-only component, then adding webc:root shouldn't cause the host component to no longer be stripped away.
Describe alternatives you've considered
No response
Additional context
No response
Contributor guide
No contributing guide indexed for this repository
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 tracing the logic that identifies HTML-only components and handles webc:root. Verify how class merging currently behaves with webc:root and webc:root="override"; done means the host element is stripped while its classes still merge without requiring the override value.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- frontend
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100