Feasability of a template plugin or core functionality?
- Dominant language
- Python
- Stars
- 15.7k
- Forks
- 2.1k
- Avg merge
- 4d 21h
- Merged PRs (30d)
- 31
Description
Recently, I wanted to add a functionality to the `play` plugin, which would allow the user (aka egocentric me) to do something like `beet play --template awesome` in order to play preconfigured queries. The configuration would look something like this:
```
play:
templates:
awesome: artist:awesome artist, album:another awesome album
```
Then I thought about some issues/possible improvements:
- It could make the `play` plugin too big and not focused enough to some people's taste (including me kind of).
- I think several other commands/use cases could use this kind of functionality.
So from there I think there are three possibilities:
- Only add this functionality to play, disregarding the two previous points.
- Add this functionality to the core.
- Create a `template` plugin to enable this functionality beets wide.
Out of those three, the last option seduces me most. However, I don't know if a plugin would be able to add command line flags to all existing commands.
What's your take on this? I'd love to hear opinion and how you would use (or not use) this functionality.
Contributor guide
Assessment
This issue has not been assessed yet.