Repository navigation
docs: clarify UIManager LayoutAnimation scope and New Architecture behaviour. - #5262
Conversation
|
Thank you for your pull request and welcome to our community. Action RequiredIn order to merge any pull request (code, docs, etc.), we require contributors to sign our Contributor License Agreement, and we don't seem to have one on file for you. ProcessIn order for us to review and merge your suggested changes, please sign at https://code.facebook.com/cla. If you are contributing on behalf of someone else (eg your employer), the individual CLA may not be sufficient and your employer may need to sign the corporate CLA. Once the CLA is signed, our tooling will perform checks and validations. Afterwards, the pull request will be tagged with If you have received this in error or have any questions, please contact us at cla@meta.com. Thanks! |
|
Thank you for signing our Contributor License Agreement. We can now accept your code for this (and any) Meta Open Source project. Thanks! |
There was a problem hiding this comment.
Hello @supunyasanthaofficial, thanks for the update on this! 👍
Since you edited only the docs file the change would be visible only in "Next" docs and in future React Native versioned docs. If you want this change to apply to older, already present versioned docs, you would need to backport your changes:
Preview
Fixes #889
Summary
Clarifies the use of
UIManager.setLayoutAnimationEnabledExperimentalindocs/layoutanimation.md:Clarifies that on Android with the Legacy Architecture, this flag enables layout animations globally and only needs to be called once (for example, in the app's root entry file
index.jsor root component) before triggering layout animations, rather than per component.Adds a note clarifying that on the New Architecture, layout animations work automatically and calling
setLayoutAnimationEnabledExperimentalis unnecessary (it is a no-op).Test Plan