linkedin / linkedin/css-blocks
resolving against a style that inherits
Open
- Dominant language
- TypeScript
- Stars
- 6.3k
- Forks
- 154
- PR merge metrics
- No merged PRs in 30d
Description
I think our current output for resolving against a style that has it's own resolution against a base style produces selectors of the same specificity, making us susceptible to concat order issues.
Contributor guide
Research direction
Start by reproducing the reported case where a style resolves against a base style and inspect the generated selectors and their specificity. Trace the existing style-resolution entry point, then add or update a focused test demonstrating the inheritance case; it is done when the output no longer permits concatenation-order conflicts.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- css, typescript
- Domain
- frontend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100