Skip to content

Adds cacheExtent and cacheExtentStyle migration guide#13044

Merged
sfshaza2 merged 3 commits intoflutter:mainfrom
chunhtai:scrollcacheextent
Feb 9, 2026
Merged

Adds cacheExtent and cacheExtentStyle migration guide#13044
sfshaza2 merged 3 commits intoflutter:mainfrom
chunhtai:scrollcacheextent

Conversation

@chunhtai
Copy link
Contributor

@chunhtai chunhtai commented Feb 6, 2026

migration guide for flutter/flutter#181092

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.

@chunhtai chunhtai requested review from a team and sfshaza2 as code owners February 6, 2026 23:00
@gemini-code-assist
Copy link
Contributor

Summary of Changes

Hello @chunhtai, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request focuses on enhancing the documentation for a significant breaking change within Flutter's scrolling mechanism. It provides a comprehensive migration guide for developers transitioning from the deprecated cacheExtent and cacheExtentStyle properties to the new scrollCacheExtent property. The guide details how to update both widget and RenderObject layer implementations, ensuring a smoother upgrade path and promoting the use of a more explicit and type-safe API for scroll caching.

Highlights

  • New Migration Guide Added: This pull request introduces a new migration guide document for the deprecation of cacheExtent and cacheExtentStyle properties in Flutter's scrolling widgets.
  • Replacement Property: The deprecated properties are replaced by a new scrollCacheExtent property, which utilizes a ScrollCacheExtent object to encapsulate both the value and the caching strategy (pixels or viewport).
  • Improved Clarity and Type Safety: The change aims to provide clearer intent and better type safety by explicitly defining the caching strategy within the ScrollCacheExtent object, moving away from the previous ambiguous interpretation of a double value.

🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console.

Changelog
  • src/content/release/breaking-changes/index.md
    • Added a new entry and link for the 'Deprecated cacheExtent and cacheExtentStyle' migration guide.
  • src/content/release/breaking-changes/scroll-cache-extent.md
    • New file created, containing the detailed migration guide for the cacheExtent and cacheExtentStyle deprecation.
    • Includes sections on summary, background, migration steps for widget and RenderObject layers, timeline, and references to API documentation and the original PR.
Activity
Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature Command Description
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment @gemini-code-assist Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help /gemini help Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

  1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution.

Copy link
Contributor

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

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

Code Review

This pull request adds a migration guide for the deprecation of cacheExtent and cacheExtentStyle. The guide is well-structured and provides clear before-and-after code examples. My review includes suggestions to adhere to the project's documentation style guide, specifically regarding semantic line breaks, and to enhance the completeness of the migration examples for the RenderObject layer.

@flutter-website-bot
Copy link
Collaborator

flutter-website-bot commented Feb 6, 2026

Visit the preview URL for this PR (updated for commit f8171d0):

https://flutter-docs-prod--pr13044-scrollcacheextent-c4yk928m.web.app

Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com>
Copy link
Contributor

@sfshaza2 sfshaza2 left a comment

Choose a reason for hiding this comment

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

lgtm

@sfshaza2 sfshaza2 merged commit 7fc5bf7 into flutter:main Feb 9, 2026
10 checks passed
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.

3 participants

Comments