Skip to content

Propagate consumer fixes (MDXInstance props, git-log/fetch guards)#116

Open
hasparus wants to merge 1 commit into
mainfrom
fix/propagate-consumer-fixes
Open

Propagate consumer fixes (MDXInstance props, git-log/fetch guards)#116
hasparus wants to merge 1 commit into
mainfrom
fix/propagate-consumer-fixes

Conversation

@hasparus

@hasparus hasparus commented Jul 2, 2026

Copy link
Copy Markdown
Owner

Small template hardening for issues found while bridging these fixes into loudmouth (#53) and homepage (#63), so future syncs don't re-seed them.

  • PostLayout propsOmit<MDXInstance<{}>, "frontmatter"> & { frontmatter; headings }. The old MarkdownLayoutProps mismatches the MDX modules [...path].astro spreads; astro check (exactOptionalPropertyTypes) flags it. zaduma's typecheck is tsc --noEmit only, so it's latent here — but consumers that run astro check (loudmouth) hit it.
  • derivedTitleAndDatePlugin: execFileSync git-log now guarded — falls back to current date if git/.git is absent instead of failing the build.
  • Image.astro: throw on non-ok remote fetch instead of passing an error body to getPlaiceholder.

Verified: tsc --noEmit 0 errors, lint clean, build 10 pages.

… + remote fetch

Fixes surfaced while syncing loudmouth/homepage:
- PostLayout Props: MarkdownLayoutProps -> Omit<MDXInstance<{}>,'frontmatter'> + headings, matching the MDX page spread (astro check flags the old type under exactOptionalPropertyTypes; zaduma's tsc-only typecheck doesn't, but consumers running astro check do)
- derivedTitleAndDatePlugin: guard execFileSync git-log against missing git/.git (fall back to current date)
- Image.astro: throw on non-ok remote image responses instead of decoding an error body
@coderabbitai

coderabbitai Bot commented Jul 2, 2026

Copy link
Copy Markdown

Warning

Review limit reached

@hasparus, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 11 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

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 reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

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, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details
⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: 81b32557-22e6-4e24-a724-b0e7b3ee7599

📥 Commits

Reviewing files that changed from the base of the PR and between be33bec and a4ef298.

📒 Files selected for processing (3)
  • src/build-time/derivedTitleAndDatePlugin.tsx
  • src/layouts/PostLayout.astro
  • src/lib/prose/Image.astro
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch fix/propagate-consumer-fixes

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

Comment @coderabbitai help to get the list of available commands.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant