linkedin / linkedin/css-blocks
test cases for concatenation order independence.
Open
- Dominant language
- TypeScript
- Stars
- 6.3k
- Forks
- 154
- PR merge metrics
- No merged PRs in 30d
Description
We should use a strategy similar to opticss (before and after cascade comparison) to verify that concatenation order changes don't break css-blocks's resolution.
Contributor guide
Research direction
Start by reviewing css-blocks's cascade-resolution behavior and opticss's before-and-after cascade comparison approach. Locate the existing resolution test entry points, then define cases covering changed concatenation order. Done means the tests verify that concatenation order changes do not alter css-blocks's resolution.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- css, typescript
- Domain
- frontend, testing
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100