Add native spring easing for motion and style transitions - #207
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Fixes #196.
Summary
{ type: "spring", stiffness?, damping?, mass?, velocity? }easing object to bothMotionTransition.easeandStyleTransition.easinglinear()easingThe object wire format deliberately matches remorses/gpuix#34 for reconciliation, while this implementation keeps the existing native track machinery and adds no JavaScript frame loop. Defaults are Motion's
100 / 10 / 1, and springs are available on both motion targets and state-style transitions.Verification
bun run build --target aarch64-apple-darwininpackages/nativebun run testinpackages/react: 719 passed, 0 failed, 0 skipped (42 files)bun run testinexamples: 54 passed, 0 failed, 0 skipped (7 files)cargo test --libinpackages/native: 344 passed, 0 failed, 0 ignored