Closed RustyNova016 closed 7 months ago
The schema was correct all along (Or else go blame lucifer on the IRC lol)
Ooops- I merged my own fork's changes in my pull request branch instead of my own branch. I'm fixing that.
As for the doc comments, I'd say either we slowly add them to types, because while inconsistent, it's better than nothing, or else we make a new branch just for them.
I merged my own fork's changes in my pull request branch instead of my own branch. I'm fixing that.
:+1:
As for the doc comments, I'd say either we slowly add them to types, because while inconsistent, it's better than nothing, or else we make a new branch just for them.
New branch/PR is probably best :smile:
By the way, the response model file is now 500 lines long. Maybe it would be better to split it up a bit?
Yeah, definitely. I'll make an issue for this.
I recreated the whole branch, much easier than to git wrangle out of this mess. See #23
Here's the implementation of this endpoint https://listenbrainz.readthedocs.io/en/latest/users/api/statistics.html#get--1-stats-release-group-(release_group_mbid)-listeners.
The schema need verification for more edge cases, but other than that it should be working.
By the way, the response model file is now 500 lines long. Maybe it would be better to split it up a bit?