1
# TODO for blissify-rs
2
3
This is a todo-list of what's left to do for blissify-rs.
4
There is quite some work left with regards to distance metrics / way to generate
5
playlists / MPD integration.
6
7
Feel free to submit a PR editing this list if you have some wishes, and to
8
ask questions if you want to tackle an item.
9
10
## Actual TODO
11
12
- Add a feature to focus on a specific feature ("I want tempo being prioritized, or timbre, or tonal features")
13
=> take advantage of the Mahalanobis distance and make it easy-ish to use
14
- Erroneous report with CUE files (see https://github.com/Polochon-street/blissify-rs/issues/48)
15
- Try to trim out the crates (it's too big rn)
16
- grep TODO and see what can be fixed
17
- Write more tests (run code coverage tools) (maybe integration tests or whatev name is?)
18
- Split tests and code (module-wise)
19
- Refactor to merge some things together
20
- A waypoint feature: go from song1 to song2, both picked by the users, in n songs, without any repetitions between playlist 1 and playlist 2
21
- A direction feature ("I want the tempo to go down or stay the same")
22
- A "song group" feature (I want to make a playlist that's in the vibe of these n songs [like 4-5])
23
- Update clap using the derive feature, and look for clap tests
24
- DRY tests/cli.rs
25
- Split up main.rs
26
- Make sure ffmpeg and symphonia are somehow exclusive (?)
27
- Convert path in config to absolute path
28
- Make `list-db` a table with as much info as possible
29
30
## Done
31
32
