Validate minified adapter exports - #401
Conversation
|
Warning Review limit reached
Next review available in: 43 minutes Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. How can I continue?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 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 configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (1)
Comment |
Merging this PR will not alter performance
Comparing Footnotes
|
What changed
ChartView,decodeFrame, andrenderStandalone.Why
The official Vite production build legitimately renames declarations. The old test asserted source spelling rather than the shipped public export contract, so it failed after a successful minified build.
Impact
The adapter asset test now follows the artifact users install and will still fail if any required public export disappears.
Validation
node js/build.mjs.venv/bin/pytest -q tests/reflex_adapter/test_assets.py— 8 passed.venv/bin/ruff check tests/reflex_adapter/test_assets.pyFixes #393