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

PP-443: Restrict cover widths #225

Merged
merged 4 commits into from
Sep 20, 2023
Merged

PP-443: Restrict cover widths #225

merged 4 commits into from
Sep 20, 2023

Conversation

io7m
Copy link
Contributor

@io7m io7m commented Sep 20, 2023

What's this do?
This sets maximum widths for covers so that very large covers can no longer break the UI.

Before:

Screenshot_20230911_104338

Screenshot_20230911_104354

After:

Screenshot_20230920_142139

Screenshot_20230920_142525

Why are we doing this? (w/ JIRA link if applicable)
https://ebce-lyrasis.atlassian.net/browse/PP-443

How should this be tested? / Do these changes have associated tests?
Try Minotaur. The book is on the front page now.

Dependencies for merging? Releasing to production?
None.

Have you updated the changelog?
Yes.

Has the application documentation been updated for these changes?
N/A

Did someone actually run this code to verify it works?
@io7m Took the screenshots above!

This sets a maximum width for covers in lanes and book detail pages.

Affects: https://ebce-lyrasis.atlassian.net/browse/PP-443
@io7m io7m requested a review from a team September 20, 2023 14:25
Copy link
Contributor

@nunommts nunommts left a comment

Choose a reason for hiding this comment

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

Just a comment on a minor issue


<androidx.cardview.widget.CardView
<LinearLayout xmlns:android="http://schemas.android.com/apk/res/android"
Copy link
Contributor

Choose a reason for hiding this comment

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

Since there's just a CardView, do we need a parent view? If so, maybe we should use a FrameLayout instead then

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I freely admit I have no idea. I've not looked at any of the UI code for years, and even then, I wasn't the person who wrote it.

What arrangement of layouts were you thinking of?

<FrameLayout>
  <CardView>
    <ImageView/>
  </CardView>
</FrameLayout>

Like that?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Removing the parent view completely seems to work fine!

Copy link
Contributor

Choose a reason for hiding this comment

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

Cool! But for the record, I was thinking about this (like you said), if we were not to remove the parent view:

<FrameLayout>
  <CardView>
    <ImageView/>
  </CardView>
</FrameLayout>

Copy link
Contributor

@nunommts nunommts left a comment

Choose a reason for hiding this comment

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

Just a comment on a minor issue

@io7m io7m merged commit 78c8bef into main Sep 20, 2023
1 check passed
@io7m io7m deleted the feature/pp-443 branch September 20, 2023 16:29
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants