Repository navigation
docs: state since which version each CSS transition property is routed to the platform - #10549
Conversation
|
Note Reviews pausedIt looks like this branch is under active development. To avoid overwhelming you with review comments due to an influx of new commits, CodeRabbit has automatically paused this review. You can configure this behavior by changing the Use the following commands to manage reviews:
Use the checkboxes below for quick actions:
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Repository UI Review profile: CHILL Plan: Advanced Run ID: 📒 Files selected for processing (1)
Included review availability: Your plan provides up to 10 included reviews per hour; 3 remain after this review. 📝 WalkthroughWalkthroughThe feature flag guide replaces platform support markers with Reanimated version information for CSS property routing. It documents numeric-only routing for Priority: ⬇️ Low Change: Other Merge Risk: ⚪ Minimal · up to This documentation-only change does not alter runtime behavior, and its routing claims are consistent with the cited implementation. 🚥 Pre-merge checks | ✅ 4✅ Passed checks (4 passed)
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 |
There was a problem hiding this comment.
Actionable comments posted: 1
ℹ️ Review info
⚙️ Run configuration
Configuration used: Repository UI
Review profile: CHILL
Plan: Advanced
Run ID: c6c5a1d3-09bb-4ba8-a28d-9ca9d69f881e
📒 Files selected for processing (1)
docs/docs-reanimated/docs/guides/feature-flags.md
Included review availability: Your plan provides up to 10 included reviews per hour; 7 remain after this review.
There was a problem hiding this comment.
🟡 Minor · Keep borderWidth in the iOS routing documentation.
docs/docs-reanimated/docs/guides/feature-flags.md:173-178
🎯 Functional Correctness | 🟡 Minor | ⚡ Quick winKeep
borderWidthin the iOS routing documentation. WhenIOS_CSS_CORE_ANIMATIONis enabled with an eligible easing, the iOS router includesborderWidth. If React Native rasterizes the border, its width can snap instead of animating. KeepborderWidthin the iOS table and limitation warning.
ℹ️ Review info
⚙️ Run configuration
Configuration used: Repository UI
Review profile: CHILL
Plan: Advanced
Run ID: cf4df6e6-c527-4048-a62a-db1de4993d4c
📒 Files selected for processing (1)
docs/docs-reanimated/docs/guides/feature-flags.md
Included review availability: Your plan provides up to 10 included reviews per hour; 7 remain after this review.
…atform-routing-versions # Conflicts: # docs/docs-reanimated/docs/guides/feature-flags.md
Note
This pull request was authored by AI on behalf of @MatiPl01.
Summary
The "Properties routed to the platform" table in the feature flags guide was stale: it still showed
backgroundColor,borderColorandborderRadiusas not routed on Android after #10310, and gave no idea of which release routes what. Each cell now names the version since which the property is routed (iOS:opacity4.4.0, the rest 4.5.0; Android:opacity4.6.0,backgroundColor/borderColor/borderRadius/shadowColor4.7.0), and the note below the table spells out the same per platform.The
shadowColorrow for Android assumes #10547 lands in 4.7.0.Test plan
Docs-only.
remarkleaves the file unchanged.