chore: Enforce consistent SVG asset import naming#7231
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
Note Reviews pausedIt looks like this branch is under active development. To avoid overwhelming you with review comments due to an influx of new commits, CodeRabbit has automatically paused this review. You can configure this behavior by changing the Use the following commands to manage reviews:
Use the checkboxes below for quick actions:
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Repository UI Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (12)
💤 Files with no reviewable changes (2)
✅ Files skipped from review due to trivial changes (7)
🚧 Files skipped from review as they are similar to previous changes (3)
WalkthroughStandardizes many image/SVG import bindings to ChangesTooling & Codemod
Repository-wide Asset Renames
Estimated code review effort🎯 4 (Complex) | ⏱️ ~45 minutes
🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches📝 Generate docstrings
🧪 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 |
Deploying swap-dev with
|
| Latest commit: |
5afd7dd
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://4f76c2f3.swap-dev-5u6.pages.dev |
| Branch Preview URL: | https://feat-173-svg-import-naming.swap-dev-5u6.pages.dev |
Summary
Decided to implement this after #7206 so that SVG assets are imported with consistent naming so that it's a bit more obvious what they are (they are simple paths / URLs, but some looked like components when written in CamelCase, some other ones where in UPPER_CASE...).
This commit fixes the linting issues (renames SVG imports): 0e35c94
To Test
Nothing to test.
Summary by CodeRabbit