fix: wrap long dataset titles to prevent horizontal overflow#7
Conversation
|
@clombion is attempting to deploy a commit to the Datopian Team on Vercel. A member of the Team first needs to authorize it. |
|
Warning Review limit reached
Next review available in: 54 minutes Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (5)
📝 WalkthroughWalkthroughUpdated Tailwind classes to wrap long titles and constrain dataset card and search-result layouts across shared, home, and search components. ChangesResponsive text wrapping
Estimated code review effort: 1 (Trivial) | ~5 minutes Possibly related PRs
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
A dataset title with a long unbroken token (e.g. a filename-style slug) had no break opportunity, so it stretched its container past the viewport width. On the dataset page the title ran off-screen; on the mobile home page it widened a card in the latest-datasets grid, pushing the whole document wider than the viewport so the hero no longer spanned the screen. Wrap titles and let their grid/flex tracks shrink: - HeroSection h1, MainSection card title, DatasetItem title, and the ResourcesList resource name get break-words. - The home latest-datasets grid is single-column on mobile (grid-cols-1) with min-w-0 cards, and the search results column gets min-w-0, so a long token can no longer force a track wider than the viewport.
✅ Action performedReview finished.
|
✅ Action performedFull review finished. Your plan includes PR reviews subject to rate limits. More reviews will be available in 54 minutes. |
A dataset whose title is a long unbroken token — for example the filename-style
slug
Itie_mocambique_8o_relatorio_i2a_consultoria_versao_final_28022020_eng—has no break opportunity, so it stretches its container wider than the viewport.
On the dataset page the title runs off the right edge. On the mobile home page
the same title stretches a card in the latest-datasets grid, which pushes the
whole document wider than the screen, so the hero no longer spans the viewport
and leaves dead space to the right.
This wraps those titles and lets their grid and flex tracks shrink below their
content width, so a long token can no longer force a track wider than the
viewport.
Changes
fix: wrap long dataset titles
break-wordsto the page title (HeroSection), the home latest-datasetscard title, the search-result title (
DatasetItem), and the resource name(
ResourcesList).fix: constrain grid and flex tracks
grid-cols-1)with
min-w-0cards, and addmin-w-0to the search results column.mobile hero spans the full width again.
Test plan
viewport (DevTools:
documentScrollWidth === clientWidth).its dataset page.
eslintclean on all changed files.Summary by CodeRabbit
min-width: 0).