linkedin / linkedin/css-blocks
[glimmer-templates] Give a better error for states scoped to a class.
Open
Nobody has claimed this yet.
@css-blocks/core
bug
- Dominant language
- TypeScript
- Stars
- 6.3k
- Forks
- 154
- PR merge metrics
- No merged PRs in 30d
Description
If a user types something like:
<div class="myblock.foo" state:myblock.foo.active>
They should get an error telling them that scoping a state to a specific class isn't necessary.
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 locating the glimmer-templates handling for state syntax and reproduce the issue with the HTML snippet in this report. Done means the invalid class-scoped state form produces an error explaining that scoping a state to a specific class is unnecessary.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- css, typescript
- Domain
- frontend
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100