Šarūnas Nejus
Šarūnas Nejus
Looking at this, I thought it can't possibly be the very first time this issue is popping up, and it seems I found what I wanted to see: https://github.com/beetbox/beets/issues/1029 @sampsyo's...
This looks like a very clean solution. I'm aware that there aren't any tests - would you like to add some? This would be ideal, and they can document what...
What about something like `db_obj`? I don't see why the name shouldn't be shared - `item_fields` and `album_fields` keys make it clear what's the entity we're dealing with. Regarding field...
shush away from here @stalebot. It's been removed from the codebase now.
> I think before we'd change this, we would want to look into bumping our poetry version above v2. We're still specifying [poetry
The reason why we pinned poetry is here: https://github.com/beetbox/beets/issues/5770
Good news, guys! Apparently, `mediafile` already supports multivalued `genres` field! @dunkla you can go ahead and implement the requested changes whenever you have time. Additionally, I think, we should think...
> ## Summary of Changes > ### Addressed PR Comments > > **1. Simplify the architecture** (snejus's main comment) > > * Removed `multi_value_genres` config option from beets/config_default.yaml > >...
I want to understand what issue does this solve as this balloons its implementation complexity.
I think, we'd rather solve this when we have an issue. For now, we use it in very limited contexts (simply as a dynamic class property) and I doubt this...