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

MBS-13263: Align release titles despite indicators for cover art and data quality #3256

Merged
merged 1 commit into from May 17, 2024

Conversation

JadedBlueEyes
Copy link
Contributor

@JadedBlueEyes JadedBlueEyes commented May 3, 2024

Problem

This fixes MBS-13263 - that releases without cover art were misaligned in release group listings.

Solution

This adds a blank space the size of the icon before releases without cover art, to align them properly. To do that, it also adds a blank-icon class. It also moves data quality indicators to the right

Testing

I visually inspected the changes at /release-group/6c08878c-d6a1-37b6-84c3-9566748545c1, /release-group/16a9cef3-b470-3ae1-bf10-cc04232d3e21 and /artist/c0a1179b-b14a-4d68-a3c1-1fdab16ed602/releases using the sample database.

Documenting

These changes should not impact the documentation.

Further action

Copy link

welcome bot commented May 3, 2024

Thanks for opening your first pull request for MusicBrainz Server, and welcome to our community! 🎉
If you haven’t yet, please check out our contributing guidelines.
Someone will be reviewing your PR soon; just hang in there!
In the meantime, if you’re wondering what to do next, you can have a look at our issue tracker.

@brainzbot
Copy link
Member

Can one of the admins verify this patch?

@reosarevok
Copy link
Member

@brainzbot, add to whitelist

@reosarevok
Copy link
Member

This does seem to fix the ticket indeed (tested locally). That said, it seems strange to only change this for releases, but not for release groups (which have exactly the same issue, see https://musicbrainz.org/artist/7c7f9c94-dee8-4903-892b-6cf44652e2de) :)

I personally liked it more before too (not sure extra space makes things look better) but I can see why consistent placement is good so not against the change if it feels like an improvement to others.

@JadedBlueEyes
Copy link
Contributor Author

@reosarevok

This does seem to fix the ticket indeed (tested locally). That said, it seems strange to only change this for releases, but not for release groups (which have exactly the same issue, see https://musicbrainz.org/artist/7c7f9c94-dee8-4903-892b-6cf44652e2de) :)

I've added it for release groups as well now, although I've had some issues testing it with my local instance because it seems like the test data set doesn't have any cover art on release groups that I can find.

I personally liked it more before too (not sure extra space makes things look better) but I can see why consistent placement is good so not against the change if it feels like an improvement to others.

I can understand this. I would have liked not to have the space if there was no cover art at all, but that's a much more complex change. As is, I think it's a small but definite improvement.

Another possibility is adding a different icon - perhaps a red picture with a line through it - to signify missing cover art explicitly. This could link with MBS-5450?

@yvanzo

[code]

Thanks for the code suggestion - I've made a slightly different change so that the blank space isn't added even when the release group entity has cover art.

It might also be worth to reorder conditional blocks more logically.

I've re-shuffled the conditionals to avoid some repetition, thank you!

I've also tested it on label pages now (/label/f752481c-2e26-446f-bccf-e487aea582ed), and it seems to work well there.

Copy link
Contributor

@yvanzo yvanzo left a comment

Choose a reason for hiding this comment

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

Thank you!

  • Code changes look good (with hidden whitespace change).
  • New display looks good (with artist, label, release group pages).

Last details to update otherwise:

  1. The two commits should be squashed together and the resulting commit should be provided with a good description (more details) (to follow our GitHub guidelines).
  2. The pull request’s title and description should be updated accordingly.
  3. The linked ticket’s summary and description should be updated too.

Note: In any case, this patch won’t be merged until next Tuesday due to the upcoming database schema change which is scheduled for release on Monday.

@yvanzo
Copy link
Contributor

yvanzo commented May 9, 2024

Actually there seems to be a small glitch when there is a data quality icon for some releases and not some others. That wasn’t anticipated in the original ticket. See /artist/c0a1179b-b14a-4d68-a3c1-1fdab16ed602/releases for example.

@JadedBlueEyes
Copy link
Contributor Author

Thank you for the feedback!

Actually there seems to be a small glitch when there is a data quality icon for some releases and not some others. That wasn’t anticipated in the original ticket. See /artist/c0a1179b-b14a-4d68-a3c1-1fdab16ed602/releases for example.

I didn't notice this, thank you! I'm reluctant to add even more white space, so I tried moving the indicator to the right, which seems to work better.

Screenshot 2024-05-12 at 19-15-39 Common - Releases - MusicBrainz

Copy link
Contributor

@yvanzo yvanzo left a comment

Choose a reason for hiding this comment

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

I tried moving the indicator to the right, which seems to work better.

Much better indeed! ✨

Thank you for this additional improvement and for the screenshot.

Please look into the latest above-mentioned details. It could now be something like “Align release titles despite indicators for cover art and data quality” (then just MBS-13263: Align release titles despite indicators for the commit subject line).

This aligns release titles even where there are cover
art or data quality indicators. It does this by moving
data quality indicators to the right of the release title
and adding whitespace when there is a missing cover
art indicator.
@JadedBlueEyes
Copy link
Contributor Author

Much better indeed! ✨

Thank you for this additional improvement and for the screenshot.

Thank you!

Please look into the latest above-mentioned details. It could now be something like “Align release titles despite indicators for cover art and data quality” (then just MBS-13263: Align release titles despite indicators for the commit subject line).

I've squashed the commits now, with an appropriate commit message. I'll update the PR and ticket!

@JadedBlueEyes JadedBlueEyes changed the title MBS-13263: Add a blank space before Release titles without cover art in RGs MBS-13263: Align release titles despite indicators May 16, 2024
@JadedBlueEyes JadedBlueEyes changed the title MBS-13263: Align release titles despite indicators MBS-13263: Align release titles despite indicators for cover art and data quality May 16, 2024
Copy link
Contributor

@yvanzo yvanzo left a comment

Choose a reason for hiding this comment

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

Selenium failure can be safely ignored as it is random and unrelated to this PR; The Selenium tests did pass in build 10851 that was before the last forced push that changed nothing. 🚢

@reosarevok reosarevok merged commit 32145ef into metabrainz:master May 17, 2024
1 of 2 checks passed
Copy link

welcome bot commented May 17, 2024

Congratulations on your first merged pull request for MusicBrainz Server! 🎉
We’re very thankful for your work, and happy to count you as part of our community!

@reosarevok
Copy link
Member

Tested locally again, seems good :) Thanks!

reosarevok added a commit that referenced this pull request May 17, 2024
* master:
  Update POT files using the production database
  MBS-13577 / MBS-13578: Release filtering for missing data (#3262)
  MBS-13589: Handle Operabase /o links (#3268)
  Convert /static/scripts/release templates to use Flow component syntax
  Convert /static/scripts/relationship-editor templates to use Flow component syntax
  Convert some more /static/scripts/ templates to use Flow component syntax
  Remove seemingly useless double export
  Convert /static/scripts/edit/components templates to use Flow component syntax
  Convert /static/scripts/common/components templates to use Flow component syntax
  Drop dead code in AddEntityDialog
  Drop unneeded instance typing in hydrate input
  Convert /components templates to use Flow component syntax
  Convert /components/list templates to use Flow component syntax
  Convert /components/Aliases templates to use Flow component syntax
  Convert /layout sidebar templates to use Flow component syntax
  Convert /layout templates to use Flow component syntax
  MBS-13585: Report for non-video recordings with video relationships (#3266)
  MBS-13581: Check "renamed into" in ArtistsThatMayBeGroups (#3265)
  Convert /edit/details templates to use Flow component syntax
  Convert /edit/details/historic templates to use Flow component syntax
  Convert /edit/component templates to use Flow component syntax
  Convert /edit templates to use Flow component syntax
  Update React to 18.3.1 (#3249)
  MBS-13263: Align release titles despite indicators (#3256)
  MBS-13588: Relationship phrase groups with pending edits are sometimes not highlighted
  Add `PendingEditsRoleT` to `RelatableEntityRoleT`
  Make `Entity::Artist::TO_JSON` consistent with `ArtistT`
  Use consistent chained method formatting
  Cache pending requests for `getOrFetchRecentItems`
  MBS-12741: Convert Create/Edit attribute admin pages to React
  Fix typo
  Limit `getReleaseGroupRecordings` to 5 attempts
  MBS-13558: Convert /report templates to use Flow component syntax
  MBS-13558: Convert /report/component templates to use Flow component syntax
  MBS-13573: Support a second format of Ticketmaster links
  MBS-13572: Support LiveNation links with _ and -
  MBS-13559: Don't reject dailysomething Bandcamp pages (#3255)
  Add context to newly added [removed] (#3246)
  Reuse same 'view list' string everywhere (#3247)
  Document that language packs must be installed
  Fix installing translations for beta/test websites
  admin/cron/hourly-sitemaps.sh: Dump FKs from READONLY
  Add missing scripts required by JSON dumps/sitemaps
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
4 participants