Plugin developers: Adapt to recent beets core changes (decargs, library restructure)

[JOJ0]

Dear plugin developers, due to recent changes in beets core, changes similar to these one's might be required to get your plugins functional again:

https://github.com/adamjakab/BeetsPluginDescribe/pull/7/files

FYI @semohr @snejus @wisp3rwind not sure if a discussion is that right place for this info. Just wanted to note somewhere that it's easy to fix/adapt.

[snejus]

Good point, thanks for raising this @JOJ0. I am responsible for both decargs removal and the migration of types. I failed to add these changes to the changelog, which I think is the best method to communicate to plugin developers.

To minimize issues, do you reckon it would be worth supporting the relevant types imports from library and to add the decargs function back, at least before we do a major version upgrade?

[JOJ0]

hmm maybe add them back but with a big fat deprecation warning and hints how to import them properly? or just with a link to where to find that fixing info?

[snejus]

See #5892

[arsaboo]

I have so many plugins 🙈...hopefully, it will not be a significant issue to update them.

[JOJ0]

for now you don't need to do anything. read this: #5892 (comment)

[arsaboo]

Yeah...I was referring to some of the plugins that I manage (Plexsync, beets-youtube, beets-subsonic, and beets-jiosaavn)

[JOJ0]

Shouldn't be much. Look at the PR for beets-describe in my initial post