Automatic or utility transition classes
- Dominant language
- Sass
- Stars
- 164
- Forks
- 26
- PR merge metrics
- No merged PRs in 30d
Description
Some utility classes such as `.opacity-100` would seemingly almost always benefit from a transition being added to it. `transition: opacity $animate-speed`.
The problems occur with the fact that transitions don't add to each other but instead overrule the past rules:
```
transition: opacity 1s;
transition: transform 1s;
```
is not equivalent to
`transition: opacity 1s, transform 1s;`
Should a transition be automatically be added to certain utility classes like `,opacity-100`, `.opacity-0`, and `.rotate-180`? Or perhaps there are transition utility classes like `.transition-opacity`?
Contributor guide
No contributing guide indexed for this repository
Research direction
Review the utility classes named in the issue, including .opacity-100, .opacity-0, and .rotate-180, along with the transition declarations shown. Done means establishing whether transitions should be added automatically or exposed through separate transition utility classes.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- css, sass
- Domain
- frontend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100