docs(compute): keep "$1.00 / 1M requests" rate on one line#7953
Conversation
The Requests rate was the longest price string and wrapped mid-value
in the rates table ("$1.00 / 1M" then "requests" on a second line).
Replace its spaces with non-breaking spaces so the rate stays intact.
The longer example-table code spans are left breakable.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
🍈 Lychee Link Check Report8 links: ✅ All links are working!Full Statistics Table
|
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (1)
WalkthroughA single character-level typography fix in the compute pricing docs: the "Requests" row of the Expected usage rates table now uses consistent non-breaking spaces in the ChangesCompute Pricing Docs — Typography Fix
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~1 minute 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. Comment |
|
The latest updates on your projects. Learn more about Argos notifications ↗︎
|
What
Fixes a layout glitch in the Prisma Compute pricing rates table: the Requests rate (
$1.00 / 1M requests) is the longest price string and was wrapping mid-value —$1.00 / 1Mon one line andrequestson the next.How
Replaced the regular spaces inside that one code span with non-breaking spaces (U+00A0) so the rate stays on a single line. Rendering is visually identical to the other rates; only the wrap behavior changes.
The longer code spans in the example-cost tables are intentionally left breakable, so this change is scoped to just the one cell.
🤖 Generated with Claude Code
Summary by CodeRabbit