cleanup

[ComputelessComputer]

No description provided.

[coderabbitai]

Warning

Rate limit exceeded

@ComputelessComputer has exceeded the limit for the number of commits or files that can be reviewed per hour. Please wait 16 minutes and 27 seconds before requesting another review.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

📥 Commits

Reviewing files that changed from the base of the PR and between 451359a and ed04cc8.

📒 Files selected for processing (3)

• apps/web/content-collections.ts (1 hunks)
• apps/web/content/docs/index.mdx (1 hunks)
• apps/web/src/routes/_view/blog/index.tsx (1 hunks)

📝 Walkthrough

Walkthrough

Schema modification making coverImage required for articles and removing runtime derivation logic, image source migration to Supabase URLs with CSS class additions, Tailwind utility refinement for flexbox behavior, and removal of SearchAndReplace editor extension.

Changes

Cohort / File(s)	Summary
Content schema and collection configuration apps/web/content-collections.ts	Changed coverImage field from optional to required in articles schema; removed runtime logic that computed coverImage from filesystem and excluded it from returned document objects.
Content documentation apps/web/content/docs/index.mdx	Updated image sources for signature-dark.svg and signature-light.svg from local paths to Supabase remote URLs; added border-none! CSS class to both <img> elements.
Blog UI styling apps/web/src/routes/_view/blog/index.tsx	Modified time element Tailwind class from flex-shrink-0 to shrink-0 in ArticleListItem rendering.
Editor extension configuration packages/tiptap/src/shared/extensions/index.ts	Removed SearchAndReplace extension import and its configuration call from getExtensions return array.

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~20 minutes

• Primary attention area: Verify that all existing articles have coverImage field populated in their frontmatter, as this field is now required in the schema and will cause validation errors if missing.
• Secondary review points: Confirm Supabase URLs are accessible and that image asset migration is complete; validate that the CSS class addition doesn't introduce unintended styling side effects; confirm SearchAndReplace extension removal doesn't affect existing user workflows.

Possibly related PRs

• blog beautify #1613: Removes article cover-image and card rendering logic while adjusting image handling — complements this PR's schema-level changes by updating corresponding UI components and display logic.

Suggested reviewers

• yujonglee

Pre-merge checks and finishing touches

❌ Failed checks (1 warning, 1 inconclusive)

Check name	Status	Explanation	Resolution
Description check	⚠️ Warning	The pull request description is completely empty with no author-provided explanation. While this is a lenient check, without any description at all, there is no meaningful information provided about the changeset. The absence of any description, even a minimal one, makes it impossible to verify if the changes are intentional and well-understood.	Add a pull request description that explains the rationale behind the changes. Include information about why coverImage is now required, why the SearchAndReplace extension was removed, and what the other minor updates accomplish. This will help reviewers understand the intent and verify the changes are correct.
Title check	❓ Inconclusive	The pull request title 'cleanup' is overly vague and generic. While the changeset does include some cleanup activities (removing unused SearchAndReplace import, updating CSS classes, and making coverImage required), the title does not meaningfully convey the nature or scope of these changes. A reader scanning the commit history would not understand what was actually changed without examining the full diff.	Consider using a more descriptive title that captures the main changes, such as 'Remove SearchAndReplace extension and update article schema' or 'Refactor image sources and schema validation'. This would provide better context for future reference and code archaeology.

---

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.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}