Skip to content

*Breaking change* Deprecate CurvedAnimation.reverseCurve in favor of AsymmetricCurvedAnimation#13347

Draft
adil192 wants to merge 1 commit intoflutter:mainfrom
adil192:breaking-changes/deprecate-curved-animation-reverse-curve
Draft

*Breaking change* Deprecate CurvedAnimation.reverseCurve in favor of AsymmetricCurvedAnimation#13347
adil192 wants to merge 1 commit intoflutter:mainfrom
adil192:breaking-changes/deprecate-curved-animation-reverse-curve

Conversation

@adil192
Copy link
Copy Markdown

@adil192 adil192 commented May 3, 2026

Description of what this PR is changing or adding, and why:

Adds a migration guide for a breaking change in flutter/flutter#185797.

PRs or commits this PR depends on (if any):

Presubmit checklist

  • If you are unwilling, or unable, to sign the CLA, even for a tiny, one-word PR, please file an issue instead of a PR.
  • If this PR is not meant to land until a future stable release, mark it as draft with an explanation.
  • This PR follows the Google Developer Documentation Style Guidelines—for example, it doesn't use i.e. or e.g., and it avoids I and we (first-person pronouns).
  • This PR uses semantic line breaks
    of 80 characters or fewer.

@adil192 adil192 force-pushed the breaking-changes/deprecate-curved-animation-reverse-curve branch from b0943d1 to f17a81a Compare May 5, 2026 23:28
@loic-sharma loic-sharma self-requested a review May 5, 2026 23:42
Comment on lines +15 to +16
If needed,
switch from [`CurvedAnimation`][] to [`AsymmetricCurvedAnimation`][].
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
If needed,
switch from [`CurvedAnimation`][] to [`AsymmetricCurvedAnimation`][].
To use distinct curves for forward and reverse directions, switch from [`CurvedAnimation`][] to [`AsymmetricCurvedAnimation`][].

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants