mirror of
https://github.com/librespot-org/librespot.git
synced 2026-04-27 08:15:50 +03:00
[GH-ISSUE #208] Get rid of Rust fmt #142
Labels
No labels
A-Alsa
SpotifyAPI
Tokio 1.0
audio
bug
can't reproduce
compilation
dependencies
duplicate
enhancement
good first issue
help wanted
high priority
imported
imported
invalid
new api
pull-request
question
reverse engineering
wiki
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/librespot#142
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @sashahilton00 on GitHub (Apr 24, 2018).
Original GitHub issue: https://github.com/librespot-org/librespot/issues/208
Rust fmt does not seem to be as stable as we thought it was. I think it would be better if we just disable it on travis and wait for things to stabilse. The recommendation would still be to run rust fmt on commits, but it would mitigate these cases where PR's have to be updated due to formatting.
@plietar commented on GitHub (Apr 24, 2018):
I agree, this was a mistake. Sorry.
We could instead of requiring the entire codebase to be always properly formatted only require it for files which have been modified.
This can still cause issues, but less frequently than in today's situation. Ultimately we would want to only check the lines that have been touched by the PR, but rustfmt doesn't support this yet.
@sashahilton00 commented on GitHub (Apr 25, 2018):
Removed from travis in
github.com/librespot-org/librespot@d76d9725e0