Skip to content

fix: cacheExtent deprecation warning across Flutter versions - #1615

Merged
daohoangson merged 5 commits into
masterfrom
codex/fix-cache-extent-deprecation
Aug 19, 2026
Merged

fix: cacheExtent deprecation warning across Flutter versions#1615
daohoangson merged 5 commits into
masterfrom
codex/fix-cache-extent-deprecation

Conversation

@daohoangson

Copy link
Copy Markdown
Owner
  • Suppress the cacheExtent deprecation warning in the anchor test.
  • Keep using cacheExtent for compatibility with the minimum supported Flutter SDK.
  • Add a TODO to migrate to scrollCacheExtent once the minimum Flutter version reaches 3.41.

Using scrollCacheExtent directly would break backward-compatibility checks because that parameter is unavailable in older supported Flutter versions.

Copilot AI lite review requested due to automatic review settings August 18, 2026 15:52

Copilot AI left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Pull request overview

Updates the core package’s anchor test to avoid a cacheExtent deprecation warning while preserving compatibility with the project’s minimum supported Flutter SDK (where the replacement API isn’t available yet).

Changes:

  • Adds an inline ignore to suppress the deprecated_member_use warning for CustomScrollView.cacheExtent.
  • Adds a TODO noting the planned migration to scrollCacheExtent once the minimum Flutter version reaches 3.41.

💡 Add a code-review agent skill for context-aware, tailored reviews. Learn more in the docs.

@github-actions

github-actions Bot commented Aug 18, 2026

Copy link
Copy Markdown

@daohoangson
daohoangson merged commit 04a3085 into master Aug 19, 2026
25 of 28 checks passed
@daohoangson
daohoangson deleted the codex/fix-cache-extent-deprecation branch August 19, 2026 14:48
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