[codex] Add blog search and category sidebar#25
Conversation
|
🚀 Preview deployed: https://codex/blog-search-category-sidebar.capacitor-tutorial.pages.dev |
|
Warning Review limit reached
More reviews will be available in 49 minutes and 36 seconds. Learn how PR review limits work. Your organization has used up its prepaid credits, and credit purchases are no longer available. Enable the review add-on in the billing tab to keep reviews running — you're only billed for reviews past your plan's rate limits ($0.25/file). ⌛ How to resolve this issue?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 credits. 🚦 How do rate limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan refill rate. 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, the refill rate gradually slows as usage increases. The highest same-day bursts are limited more strictly. Please see our Fair Usage Limits Policy for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: Organization UI Review profile: ASSERTIVE Plan: Pro Run ID: 📒 Files selected for processing (3)
📝 WalkthroughWalkthroughThe PR restructures the blog card layout to use a flex column container with updated tag/image conditional rendering and spacing, adds server-side keyword-based category classification to ChangesBlog listing search, filter, and card layout
Sequence Diagram(s)sequenceDiagram
participant User
participant SearchInput
participant CategoryButtons
participant applyFilters
participant BlogCards
participant ResultCounter
User->>SearchInput: type search query
SearchInput->>applyFilters: input event (syncs desktop ↔ mobile)
User->>CategoryButtons: click category
CategoryButtons->>applyFilters: click event (set selectedCategory, update aria-pressed)
applyFilters->>BlogCards: show/hide each card via data-category and data-search fields
applyFilters->>ResultCounter: update "Showing X articles" text
applyFilters->>BlogCards: toggle empty-state element visibility
Estimated code review effort🎯 3 (Moderate) | ⏱️ ~20 minutes 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. Comment |
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: bdf5452066
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
|
@coderabbitai review |
✅ Action performedReview finished.
|
There was a problem hiding this comment.
Actionable comments posted: 2
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@src/components/BlogListing.astro`:
- Line 168: The empty state paragraph element with data-blog-empty attribute
lacks ARIA attributes necessary for screen reader accessibility. Add
role="status" and aria-live="polite" attributes to the empty state element so
that when it becomes visible (when the hidden attribute is removed), screen
readers will announce the message to users about no articles matching their
filters.
- Around line 31-34: The getPostCategory function uses simple substring matching
which causes false positives when terms like "auth", "map", and "file" match
unrelated words like "author", "bitmap", and "profile". Additionally, including
post.id in the haystack allows file path names to trigger unintended
categorization matches. To fix this, refactor the matching logic to use
word-boundary regex patterns (escaping special characters properly) instead of
substring matching, and exclude post.id from the haystack so that only
post.data.title, post.data.description, and post.data.slug are used for
determining categories.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Organization UI
Review profile: ASSERTIVE
Plan: Pro
Run ID: ff09e182-d22a-41ef-a207-4460f2dcfdb9
📒 Files selected for processing (5)
output/playwright/blog-sidebar-desktop.webpoutput/playwright/blog-sidebar-mobile.webpsrc/components/Blog.astrosrc/components/BlogListing.astrosrc/layouts/Layout.astro
🔗 Linked repositories identified
CodeRabbit considers these linked repositories for cross-repo context during reviews:
Cap-go/capacitor-updater(manual)
|
🚀 Preview deployed: https://codex/blog-search-category-sidebar.capacitor-tutorial.pages.dev |
Summary
Screenshots
Desktop:
Mobile:
Validation
bunx prettier --write src/components/BlogListing.astro src/components/Blog.astrobun run buildSummary by CodeRabbit
New Features
Style