[CSS] single line property formatting
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 52.3k
- Forks
- 5k
- Avg merge
- 19h 2m
- Merged PRs (30d)
- 117
Description
I am re-raising this issue.
I am currently working on a CSS utility library. Almost all the classes have a single CSS property, yet they are all formatted by Prettier to take up multiple lines. For a single property, this is a massive waste of space and far less readable.
e.g. here is some code from the relatively popular [Tachyons library](e.g.: https://github.com/tachyons-css/tachyons/blob/master/css/tachyons.css):
.mt0 { margin-top: 0; }
.mt1 { margin-top: .25rem; }
.mt2 { margin-top: .5rem; }
.mt3 { margin-top: 1rem; }
.mt4 { margin-top: 2rem; }
.mt5 { margin-top: 4rem; }
.mt6 { margin-top: 8rem; }
.mt7 { margin-top: 16rem; }
Here's is what it looks like after using Prettier:
.mt0 {
margin-top: 0;
}
.mt1 {
margin-top: 0.25rem;
}
.mt2 {
margin-top: 0.5rem;
}
.mt3 {
margin-top: 1rem;
}
.mt4 {
margin-top: 2rem;
}
.mt5 {
margin-top: 4rem;
}
.mt6 {
margin-top: 8rem;
}
.mt7 {
margin-top: 16rem;
}
It is clear to me which one is preferable! Please reconsider.
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
The issue names no files, tests, or entry points. Start by reviewing the 78-comment discussion and the formatter's CSS behavior to determine the accepted scope; done would be a decided and tested formatting behavior for single-property CSS rules.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- css
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100