Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

add Add to Collection plugin #373

Merged
merged 4 commits into from
Mar 18, 2024
Merged

add Add to Collection plugin #373

merged 4 commits into from
Mar 18, 2024

Conversation

dvirtz
Copy link
Contributor

@dvirtz dvirtz commented Feb 17, 2024

This plugin adds any saved release to one of the user collections

Copy link
Member

@phw phw left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks a lot for this. This is definitely useful and it is looking good. LGTM

Overall this is some functionality that eventually should end up in Picard at some point. But at this moment I think having it as a plugin and letting that mature first is a good move.

For a future idea I think it would be cool if one could define some conditions to have saved releases end up in different collections based on some criteria. E.g. I keep my physical releases in a separate collection from the downloads.

module = obj.__module__
obj.__module__ = ".".join(module.split(".")[:-1])
yield
obj.__module__ = module
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I guess it's fine and I understand why you wanted to split this appart as you did. But it also feels a bit like over engineering for this plugin, to be honest.

Anyway, I'm fine keeping this.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I hope this limitation can be lift off in V3

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, I will look into this when I get back to the reworked plugin handling

@phw phw requested a review from zas March 18, 2024 14:26
Copy link
Collaborator

@zas zas left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

Clearly this is something Picard should handle natively, including adding one release to multiple collections.

@phw phw merged commit 0596b28 into metabrainz:2.0 Mar 18, 2024
6 checks passed
@phw phw added the new plugin label Mar 19, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants