Forward-port Pro cache API removal to main - #4543
Conversation
Remove the undocumented ReactOnRailsPro::Cache.fetch_react_component class API before 17.0.0 final, keeping supported cache behavior on the helper path and documenting the breaking change. (cherry picked from commit 793700a)
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (6)
💤 Files with no reviewable changes (2)
WalkthroughThis PR removes the public ChangesCache API removal and helper inlining
Estimated code review effort: 3 (Moderate) | ~25 minutes Possibly related PRs
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
Warning There were issues while running some tools. Please review the errors and either fix the tool's configuration or disable the tool if it's a critical failure. 🔧 ast-grep (0.44.1)react_on_rails_pro/spec/dummy/spec/helpers/react_on_rails_pro_helper_spec.rbast-grep timed out on this file 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 |
|
+ci-run-hosted |
Hosted CI RequestedTriggered 9 workflow(s) for View progress in the Actions tab. |
Greptile SummaryThis PR removes the undocumented Pro cache class API while keeping supported helper caching in place. The main changes are:
Confidence Score: 5/5This looks safe to merge.
Important Files Changed
Reviews (1): Last reviewed commit: "Remove undocumented Pro cache class API ..." | Re-trigger Greptile |
Review: Forward-port Pro cache API removal to mainOverviewClean forward-port of #4541. Removes the undocumented public Verification performed
Minor observations (non-blocking)
Risk assessmentLow risk. This is a pure move/inline of already-tested logic with no behavior change for the only real caller (the helper module itself), and it removes a previously-undocumented public API that nothing else depended on. Test coverage was carried over faithfully rather than dropped. |
Why
Forward-port the release-branch fix from #4541 onto
mainso the Pro cache API removal is present on both therelease/17.0.0train and the next mainline.Fixes #4497.
What
793700ac6763a97d5fe413ee7c64d1b56bc98e0awith-xprovenance.ReactOnRailsPro::Cache.fetch_react_componentclass API onmain.CHANGELOG.mdconflict by preserving the existing Unreleased Fix Pro streamed RSC hydration mismatch #4532 entry and making the rc.7 cache wording implementation-neutral.Validation
git diff --check origin/main...HEADruby -c react_on_rails_pro/app/helpers/react_on_rails_pro_helper.rbruby -c react_on_rails_pro/lib/react_on_rails_pro/cache.rbscript/check-pro-license-headersLANG=en_US.UTF-8 LC_ALL=en_US.UTF-8 RUBYOPT='-EUTF-8' BUNDLE_GEMFILE=react_on_rails_pro/Gemfile bundle exec rspec react_on_rails_pro/spec/react_on_rails_pro/cache_spec.rb(21 examples, 0 failures)pnpm install --frozen-lockfilepnpm exec prettier --check CHANGELOG.md(cd react_on_rails_pro/spec/dummy && pnpm run build:test)(cd react_on_rails_pro/spec/dummy && LANG=en_US.UTF-8 LC_ALL=en_US.UTF-8 RUBYOPT='-EUTF-8' bundle exec rspec spec/helpers/react_on_rails_pro_helper_spec.rb)(116 examples, 0 failures)Note: the local pre-push hook's Ruby branch lint passed, but
markdown-linksis blocked by the installed Lychee v0.24.2 failing to parse the existing.lychee.tomlinclude_fragments = falsesetting. The branch was pushed with--no-verifyafter the focused checks above passed.Summary by CodeRabbit
Breaking Changes
Bug Fixes