Repository navigation
fix: replace raw Unicode special characters with HTML entities - #16
Conversation
Use · and — instead of raw · and — across all Svelte components and page metadata for consistency and explicitness. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Team Run ID: 📒 Files selected for processing (5)
Included review availability: Your plan provides up to 1 included review per hour; 0 remain after this review. 📝 WalkthroughWalkthroughThe change replaces literal middle-dot and em-dash characters with equivalent HTML entities in component text, image alt text, and page metadata. No logic, structure, styling, or public declarations changed. ChangesHTML entity normalization
Estimated code review effort: 1 (Trivial) | ~2 minutes Merge Risk: ⚪ Minimal · up to This updates displayed punctuation and page-title metadata without changing application behavior. No current merge-readiness risk remains. 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
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 |
Summary
·) with·and em dashes (—) with—across all Svelte components and page metadata ) were already used alongside raw Unicode characters on the same lineForDevelopers.svelteandInstall.sveltewhere special characters are inside JS string literals (HTML entities would render as literal text)Files changed
Hero.svelte— 5 middle dots, 4 em dashesForPlatformEngineers.svelte— 4 em dashesOpenSource.svelte— 1 em dashFooter.svelte— 1 middle dot+page.svelte— 3 em dashes (title + meta tags)Test plan