beetbox / beetbox/beets

badfiles: config options/command for fixing files

Open
#3,126 5 comments 1 reaction 0 assignees View on GitHub
badfiles feature
Dominant language
Python
Stars
15.7k
Forks
2.1k
Avg merge
4d 21h
Merged PRs (30d)
31

Description

How about a separate config entry for commands to fix bad files instead of just listing them. Also one could possibly run a separate command (for example `beet fix` or `beet bad -f` ) to fix every file in the library instead of just checking.

Suggested config structure:
```
badfiles:
check:
mp3: mp3val
...
fix:
mp3: mp3val -f -nb
...
```

Contributor guide

Open the contributing guide

Research direction

Start by locating the existing badfiles configuration and command entry point that currently only checks files. Review how format-specific check commands are loaded and how a library-wide operation would be invoked. Done means the proposed separate fix commands and an explicit way to apply them across the library are defined and covered by appropriate behavior checks.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
cli
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.