6 of 6 standards met
Summary Upgrade GitHub Actions to their latest versions to ensure compatibility with Node 24, as Node 20 will reach end-of-life in April 2026. Changes Context Per GitHub's announcement, Node 20 is being deprecated and runners will begin using Node 24 by default starting March 4th, 2026. Why this matters Node 20 EOL: April 2026 Node 24 default: March 4th, 2026 Action**: Update to latest action versions that support Node 24 Security Note Actions that were previously pinned to commit SHAs remain pinned to SHAs (updated to the latest release SHA) to maintain the security benefits of immutable references. Testing These changes only affect CI/CD workflow configurations and should not impact application functionality. The workflows should be tested by running them on a branch before merging.
Summary The new Robolectric PAUSED LooperMode will become the default in new versions of Robolectric. We have ran all litho-it tests against the new PAUSED LooperMode and unfortunately some of them are failing. For these tests we need to explicitly specify the LooperMode as LEGACY to be future proof, so that they do not start failing when the default changes to PAUSED in the future. Changelog Add @LooperMode LEGACY in tests that fail in PAUSED LooperMode Test Plan N/A, this change only affects tests
Repository: facebook/litho. Description: A declarative framework for building efficient UIs on Android. Stars: 7778, Forks: 765. Primary language: Kotlin. Languages: Kotlin (57.6%), Java (35.2%), C++ (5%), Starlark (1.6%), JavaScript (0.2%). License: Apache-2.0. Homepage: https://fblitho.com Latest release: v0.49.1 (1y ago). Open PRs: 53, open issues: 57. Last activity: 6d ago. Community health: 87%. Top contributors: passy, astreet, mihaelao, IanChilds, pasqualeanatriello, marco-cova, zielinskimz, adityasharat, lucasr, muraziz and others.
Last 12 weeks ยท 0 commits
Summary The current setupTransitions() implementation never looks at any transitions defined on the previous LayoutState when creating AnimationBindings. This can be an issue for disappear transitions because the new LayoutState will no longer contain any disappearing items. This change adds logic in the TransitionManager to first create AnimationBindings for the previous LayoutState, then create AnimationBindings for the new LayoutState and finally merge the two. Changelog Fixes support for disappear transitions in TransitionManager Test Plan We have manually verified disappear transitions are working as expected after this change.
Summary Support for a default ScrollStateDetector n HorizontalScrollSpec and VerticalScrollSpec was added in a previous PR. This PR allows users to provide their own custom ScrollStateDetector implementation. It breaks the existing ScrollStateDetector class into two: It extracts an interface that users can potentially implement with their own functionality and also creates an additional DefaultScrollStateDetector that now contains the default implementation to be used when no custom implementation has been specified. Changelog Allow for custom ScrollStateDetector implementations in HorizontalScrollSpec and VerticalScrollSpec. Test Plan This change has been tested via unit tests