Document precompile_hook alternatives and tradeoffs#897
Conversation
|
Warning Rate limit exceeded
⌛ How to resolve this issue?After the wait time has elapsed, a review can be triggered using the 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. ✨ Finishing touches🧪 Generate unit tests (beta)
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 |
Greptile SummaryExpands the
The documentation accurately reflects the implementation in Confidence Score: 5/5
Important Files Changed
Last reviewed commit: 218fd4e |
218fd4e to
9210eae
Compare
## Summary - add a decision guide for when to use `precompile_hook` versus explicit startup orchestration in `bin/dev` - add a comparison table with tradeoffs - document how `precompile_hook` and `shakapacker_precompile` interact - call out `SHAKAPACKER_SKIP_PRECOMPILE_HOOK=true` as the temporary bypass Closes #881.
## Summary - add a decision guide for when to use `precompile_hook` versus explicit startup orchestration in `bin/dev` - add a comparison table with tradeoffs - document how `precompile_hook` and `shakapacker_precompile` interact - call out `SHAKAPACKER_SKIP_PRECOMPILE_HOOK=true` as the temporary bypass Closes #881.
Summary
precompile_hookversus explicit startup orchestration inbin/devprecompile_hookandshakapacker_precompileinteractSHAKAPACKER_SKIP_PRECOMPILE_HOOK=trueas the temporary bypassCloses #881.