-
-
Notifications
You must be signed in to change notification settings - Fork 235
chore: use spaces instead tabs #1184
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #1184 +/- ##
==========================================
- Coverage 42.35% 42.28% -0.06%
==========================================
Files 21 21
Lines 1991 1994 +3
==========================================
Hits 843 843
- Misses 1148 1151 +3
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
hard_tabs = true | ||
tab_spaces = 4 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is the main change. Everything else is automatic formatting.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Note that this PR should be either merged without squash or rebased (and this file updated to correct the hash of the commit that ends up being there).
I was thinking of creating a patch release for these formatting changes after I'm done with the current reviews. Otherwise it might be a bit annoying to rebase this on other PRs. I always forget to do this though... |
Fixing PRs should fairly simple: git checkout main -- rustfmt.toml
cargo +nightly fmt
git commit -am 'formatting
git push If you're squashing merges then this shouldn't really be too much of a problem |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
To actually apply this, I'd suggest grabbing rustfmt.toml, discarding everything else and rerunning cargo +nightly fmt
git reset --hard main
git reset fdf857422158338c9ec461270b1aabd31a375049 rustfmt.toml
cargo +nightly fmt
git commit -aC fdf857422158338c9ec461270b1aabd31a375049
git push
git reset 541aa64f4e60738b0ff24895b358c3f05a4b841e .git-blame-ignore-revs
# edit the file with the correct hash
@@ -1,8 +1,6 @@ | |||
edition = "2024" | |||
max_width = 85 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'd recommend upping this to 100 (and adding comment_width=100)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'd also recommend dropping struct_field_align_threshold
- it looks ugly as sin. Particularly for the clap config as the indentation is all over the place.
yes pls do itt |
https://www.youtube.com/watch\?v\=V7PLxL8jIl8
This brings things more in line with pretty much every rust project out there. Hard tabs are used in around 0.1% of rust projects:
hard_tabs = true
: https://github.com/search?q=path%3A%22rustfmt.toml%22+%22hard_tabs+%3D+true%22+AND+%28NOT+is%3Afork%29&type=code (1.9k results)