linkedin / linkedin/css-blocks
Conflict Warnings & Resolutions involving css variables
Open
- Dominant language
- TypeScript
- Stars
- 6.3k
- Forks
- 154
- PR merge metrics
- No merged PRs in 30d
Description
When a property's value has custom variables, the conflict detection seems to throw up its hands and just ignore the issue. When a resolution is specified towards a value that contains a css variable, the resolution value ends up being `inherit` instead.
Contributor guide
Research direction
Start by reproducing conflict detection and resolution with a property value containing a CSS custom variable. Trace the warning and resolution paths to determine why conflicts are ignored and why the resolved value becomes `inherit`; done means conflicts are reported and resolutions preserve the variable-containing value.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- css, typescript
- Domain
- frontend, tooling
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100