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

fix: sections not always respecting layout max #2109

Merged
merged 1 commit into from
Jul 15, 2024
Merged

Conversation

digitalcora
Copy link
Contributor

@digitalcora digitalcora commented Jul 12, 2024

The max field is intended as a hard limit: a higher number of rows should never be displayed (aside from Later Departures). However, if the layout already fit on the screen without overflowing on the initial render, we would never trim sections at all, including to their max.

This makes the initial conversion of a section to a "folded" section also perform the trim-to-max.


The `max` field is intended as a hard limit: a higher number of rows
should never be displayed (aside from Later Departures). However, if
the layout already fit on the screen without overflowing on the initial
render, we would never trim sections at all, including to their max.

This makes the initial conversion of a section to a "folded" section
also perform the trim-to-max.
@mbta mbta deleted a comment from github-actions bot Jul 12, 2024
@digitalcora digitalcora marked this pull request as ready for review July 12, 2024 20:12
@digitalcora digitalcora requested a review from a team as a code owner July 12, 2024 20:12
@digitalcora digitalcora merged commit 4f49193 into main Jul 15, 2024
13 checks passed
@digitalcora digitalcora deleted the cfg-trim-to-max branch July 15, 2024 17:08
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