LB-1366: Updated POST /grid/ endpoint

[07jasjeet]

Problem

LB-1366

Action

1. The endpoint now accepts release_group_mbids array.
2. Capped the number of mbids to process in a request to 100.

[pep8speaks]

Hello @07jasjeet! Thanks for updating this PR. We checked the lines you've touched for PEP 8 issues, and found:

• In the file listenbrainz/art/cover_art_generator.py:

Line 228:1: W293 blank line contains whitespace

• In the file listenbrainz/webserver/views/art_api.py:

Line 67:131: E501 line too long (131 > 130 characters)
Line 120:1: W293 blank line contains whitespace
Line 124:1: W293 blank line contains whitespace
Line 128:23: W291 trailing whitespace
Line 130:1: W293 blank line contains whitespace
Line 133:1: W293 blank line contains whitespace
Line 134:1: W293 blank line contains whitespace
Line 135:5: E303 too many blank lines (2)
Line 138:1: W293 blank line contains whitespace
Line 142:10: W291 trailing whitespace

• In the file listenbrainz/webserver/views/test/test_art.py:

Line 70:131: E501 line too long (134 > 130 characters)
Line 165:1: W293 blank line contains whitespace

Comment last updated at 2024-02-05 17:14:43 UTC

[07jasjeet]

How should I go about the tests?

• 3 tests are to be edited.
• 2 new tests (to ensure "max" logic for input mbids and mbid array itself) for the target endpoint.

[amCap1712]

I think we don't need to support having both release mbids and release group mbids. If release mbids are specified use them if not try for release group mbids.

[amCap1712]

Then depending on which entity is being used, pass the correct value (release or release-group) to

listenbrainz-server/listenbrainz/webserver/views/art_api.py

Line 125 in 0b40f9e

entity="release",

[amCap1712]

Thanks for the PR. Using both releases and release groups like this will break some links in the SVGs so instead we simplify a few things and only support release or release groups at a time but not both.