-
Notifications
You must be signed in to change notification settings - Fork 104
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
implement collection add/delete methods #175
Comments
Ian also implemented get works, and it's live on beta. No work submission though. Is there a event submit api yet? |
No clue actually. I don't follow server development closely ATM. |
This is waiting on http://tickets.musicbrainz.org/browse/MBS-8652 and http://tickets.musicbrainz.org/browse/MBS-8651 |
Signed-off-by: Alastair Porter <[email protected]>
Signed-off-by: Alastair Porter <[email protected]>
Both upstream tickets have been fixed. |
Any chance that this is implemented soon (I need it for works :) )? |
Unfortunately I think none of the usual suspects is going to implement this in the near future :( If you feel like implementing it on your own, you can probably just copy&paste https://github.com/alastair/python-musicbrainzngs/blob/master/musicbrainzngs/musicbrainz.py#L1324-L1337 and replace |
Worked out fine, thank you very much! :) |
@fin0 Would you mind submitting a pull request for those changes? |
The type of a collection was implemented in #170 and we can work with collections of releases.
After the implementation for events is complete (#168) we should also implement handling of collections of events. (blocked by #168)
There are some comments about this in #170.
The text was updated successfully, but these errors were encountered: