rdswift: There are different documentations for different audiences so different requirements. Some data is also directly documented by the server, for example relationship types or the PRs that we were discussing the other day.
monkey: I was creating an endpoint similar to "https://api.listenbrainz.org/1/popularity/top-recordings-for-artist?artist_mbid=ed3f4831-e3e0-4dc0-9381-f5649e9df221" to fetch top releases for an artist which requires data to be fetched for all releases in the backend.
2023-12-05 33923, 2023
monkey
Hm, might want to chat with mayhem about that, he's working on something similar (not the endpoint but the top albums) on our entity-pages feature branch : https://github.com/metabrainz/listenbrainz-server…
2023-12-05 33946, 2023
monkey
He might have a plan and/or pointers, but he'll need more context
2023-12-05 33933, 2023
ansh
monkey: Thanks!
2023-12-05 33920, 2023
BrainzGit
[musicbrainz-server] 14reosarevok opened pull request #3117 (03master…use-himBHsreact-fragment-type): Use React$FragmentType rather than typeof React.Fragment https://github.com/metabrainz/musicbrainz-server/…
yvanzo: btw, obviously not a priority today, but https://github.com/metabrainz/musicbrainz-server/… would be a nice one to review for the next release after this maybe if you can because it gets really annoying to have to downvote spammers and wait for their stuff to go away :)
