Analysis of attribute presence
Open
Nobody has claimed this yet.
help wanted
pkg:element-analysis
- Dominant language
- TypeScript
- Stars
- 713
- Forks
- 23
- PR merge metrics
- No merged PRs in 30d
Description
There's not currently a way to represent an attribute as being present or not. The workaround right now would be use use a constant with an empty string as a value, but I'm not sure that would be interpreted correctly by the selector matching code.
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 tracing the selector matching code referenced in the issue and how attributes are currently represented. Define and implement a representation for attribute presence or absence, then verify that selector matching interprets it correctly, including the proposed empty-string workaround.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- css, typescript
- Domain
- frontend, tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100