feat(ui): add 'show more/less...' for studios on movie details page

[dphildebrandt]

Description

Display a max of 3 studios before prompting to expand the list

Screenshot (if UI-related)

To-Dos

• Successful build yarn build
• Translation keys yarn i18n:extract

Issues Fixed or Closed

• Fixes Small enhancement for the studio list on detail page #1489

[TheCatLady]

We should never use ... instead of the ellipsis character, but I don't really think this looks great as text. Perhaps an icon would look better? Solid variants of chevron-double-down/chevron-double-up maybe? Or the dots-horizontal icon? 🤔

[sct]

We should never use ... instead of the ellipsis character, but I don't really think this looks great as text. Perhaps an icon would look better? Solid variants of chevron-double-down/chevron-double-up maybe? Or the dots-horizontal icon? 🤔

Chevron would be better for this I feel. We should also change the color to indicate the user can interact with this and its just not another studio?

[TheCatLady]

Chevron would be better for this I feel. We should also change the color to indicate the user can interact with this and its just not another studio?

Well, FWIW users can interact with the studios in the list as well 😛

[sct]

Chevron would be better for this I feel. We should also change the color to indicate the user can interact with this and its just not another studio?

Well, FWIW users can interact with the studios in the list as well 😛

True, the icon may be enough to differentiate it.

[dphildebrandt]

Updated screenshot in PR body.

[TheCatLady]

@dphildebrandt You don't need to squash your commits down btw, we squash before merging anyway 😄 Makes it hard to tell what changed when you do that.

[dphildebrandt]

@dphildebrandt You don't need to squash your commits down btw, we squash before merging anyway 😄 Makes it hard to tell what changed when you do that.

Ah, I wasn't sure. I was trying to keep the commits atomic, and didn't think some of these changes warranted a full-blown husky-compatible commit message.

[TheCatLady]

Ah, I wasn't sure. I was trying to keep the commits atomic, and didn't think some of these changes warranted a full-blown husky-compatible commit message.

I think that it makes it harder to difficult to review and see what changed since the last time we viewed the PR. Best to just add separate commits, especially once you've opened a PR and people have begun reviewing it.

[sct]

Sorry for the long wait! Things have been super busy!

Looks great! Thanks for the contribution again!

[github-actions]

🎉 This PR is included in version 1.26.0 🎉

The release is available on:

• v1.26.0
• GitHub release

Your semantic-release bot 📦🚀