No actionable comments were generated in the recent review. 🎉

Walkthrough

Documentation clarifications for React Server Components in streaming SSR patterns, Rails controller setup simplification, and minor wording adjustments for consistency. No functional code changes.

Changes

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Poem

🐰 A hop, skip and edit so fine,
Docs clarified, every line in line,
React Server magic, now plain to see,
Rails setup simpler, as it should be!
Our streaming flows dance with delight! ✨

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 @coderabbitai help to get the list of available commands and usage tips.}

Review

Overall these are good, targeted clarifications. Three things worth addressing before merge:

1. React version inconsistency (streaming-ssr.md line 3)
Changing to "React 19's renderToPipeableStream" conflicts with at least 5 other doc files that still say "React 18's" or "React 18/19's". More importantly, renderToPipeableStream shipped in React 18 — attributing it to React 19 is factually off. Either update all the other files to match, or revert this line to "React 18/19's" for accuracy and consistency. (Inline comment on line 3.)

2. RSC tutorial link is the wrong destination for non-RSC users (streaming-ssr.md line 78)
The note correctly flags that async function components require RSC — but then sends non-RSC streaming users to the RSC tutorial, which is about setting up a different, more complex feature. This is likely to confuse people looking for a simpler path. The link should either go to data-fetching documentation (React Query / SWR + Suspense patterns) or be reworded to make clear the RSC tutorial is for users who want RSC, not an alternative. (Inline comment on line 78.)

3. ActionController::Live inclusion claim needs verification (streaming-ssr.md lines 110–111)
The new comment states ActionController::Live is "already mixed in by ReactOnRailsPro::Stream". If users remove their explicit include ActionController::Live based on this documentation and it turns out to be an unstable internal detail, they'll see broken streaming in production. Please confirm this is a deliberate, tested public guarantee of the ReactOnRailsPro::Stream module — not just a current implementation detail. (Inline comment on lines 110–111.)

Fragment caching change (fragment-caching.md) looks good — the rewrite is clearer and the explicit distinction between prerender: true and client-only calls is helpful.

Greptile Summary

This PR is a focused documentation polish pass on streaming-ssr.md and fragment-caching.md, addressing review feedback from #2800. All changes are docs-only with no code impact.

Key changes:

• React version consistency — "React 18/19's renderToPipeableStream" narrowed to "React 19's" to match the React 19 prerequisite; "React 18's Selective Hydration" generalized to "React's Selective Hydration" (two occurrences)
• Async component clarification — Added a callout noting that async () => {} Server Components require RSC infrastructure, pointing users toward React Query/SWR + <Suspense> for non-RSC streaming
• Fragment caching deploy note — Rewritten paragraph now explicitly contrasts prerender: true (bundle digest auto-included in key → auto-invalidated on deploy) vs. client-only calls (no digest → manual versioning required)
• Controller example simplified — Removed the explicit include ActionController::Live line (confirmed it is already mixed in by ReactOnRailsPro::Stream via its included block) and replaced it with an explanatory comment
• Style nits — "full page reload" → "full-page reload" hyphenation corrected

Confidence Score: 5/5

• Documentation-only PR with accurate, verified content — safe to merge.
• All factual claims were verified against source code: ActionController::Live is indeed auto-included by ReactOnRailsPro::Stream's included block, the RSC tutorial link resolves to an existing file, and the cache key behavior for prerender: true vs. client-only calls matches the implementation. The one P2 style note (RSC tutorial link context) is non-blocking and would simply improve clarity for the reader.
• No files require special attention.

Important Files Changed

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    A[Controller includes ReactOnRailsPro::Stream] --> B[ActionController::Live auto-mixed in]
    A --> C[stream_view_containing_react_components called]
    C --> D[render_to_string builds template]
    D --> E{Component type?}
    E -->|Async Server Component / RSC| F[Requires RSC infrastructure\nsee RSC tutorial]
    E -->|Client Component with Suspense| G[Use React Query / SWR\n+ Suspense boundary]
    C --> H[React renderToPipeableStream\nstreams HTML chunks]
    H --> I[Browser renders updates\nwithout full-page reload]
    I --> J[React Selective Hydration\nhydrates chunks as they arrive]

_{Reviews (1): Last reviewed commit: "Docs: fix streaming SSR and fragment cac..." | Re-trigger Greptile}

Review Summary

The second commit addresses the key concerns from the previous review round well. Here's my assessment of the final state:

What was addressed:

• ✅ React version: Correctly reverted back to "React 18/19's renderToPipeableStream" (the API shipped in React 18, not 19)
• ✅ RSC tutorial link: Now clearly scoped to RSC users ("For RSC-based streaming (which does support async components), see the RSC tutorial") — non-RSC users are directed to React Query/SWR + Suspense instead
• ✅ RSC tutorial link resolves to an existing file (docs/pro/react-server-components/tutorial.md)

Remaining changes look good:

• ActionController::Live comment (lines 110–111): The comment stating it's "already mixed in by ReactOnRailsPro::Stream" has been independently verified against the source code by greptile. Accurate.
• "React's Selective Hydration" (lines 258, 342): Making this version-agnostic is the right call — Selective Hydration is not exclusive to React 18.
• "full-page reload" hyphenation: Correct.

Minor observation: The code example in Step 2 (SlowDataComponent as an async function) demonstrates an RSC-only pattern, which is now called out clearly in the added note. However, it's slightly awkward that the non-RSC streaming tutorial shows code that won't work without RSC. A future improvement would be to either replace the example with a Suspense + data-fetching pattern for non-RSC users, or split the tutorial into RSC and non-RSC tracks. Not a blocker for this PR.

Overall, the documentation is more accurate and clearer after these changes. Ready to merge.