Sebastian Mohr

I'm normally using react and bundling with vite, which works very similar. Static files are transpiled for the production mode while one can run a node server for development. In...

You're right that most plugins don’t fully leverage type hints yet. Before merging additional typing-related PRs like #5734 or #5716, I thought it might be worth configuring some stricter mypy...

Hi, thank you for the report! That is a good find. I just checked the [relevant code](https://github.com/beetbox/beets/blob/8fd20b9b6774509c7f1846d2cf3b3e56acea03ea/beets/ui/__init__.py#L1634) and in theory we do resolve the `pluginpath` config option as string sequence....

The issue is about multiple `pluginpaths`. E.g. adding a folder with your own plugins. As mentioned above: > In all cases delivered plugins were found (e.g. the delivered beetsplug directory...

I just tried to reproduce this and I failed to do so. I'm loading plugins from different folders without any issue Here my config (notice the `myawesomeplugin` line) ```yaml #...

If I remove the `test` pluginpath the plugin is not found anymore (as expected). For me everything seems to be in order 🤔 ``` ** error loading plugin myawesomeplugin: Traceback...

To kick this of a bit and get us going I created a list of all the plugins that are currently in the beets docs. **Feel free to edit this...

Do you feel like this was addressed? We had quite some related PRs recently. We log the plugin name if it raises an error during import (see [here](https://github.com/beetbox/beets/blob/b06f3f6aa6e29ce3bd3f84f18ee3ff0cf5cef470/beets/plugins.py#L392)). We also...

> You may want to consider updating your (dependent) branches with `git rebase` + force pushes rather than `git merge`. GitHub seems to support it a bit better, for example,...

> Good stuff! I added a couple of comments in the interfaces, however I'm unable to see how this affects the plugins because they have also been refactored. > >...