Rename onPressed to nextArticleCallback in ArticlePage

[warioddly]

Description of what this PR is changing or adding, and why:
Rename onPressed to nextArticleCallback in ArticlePage

Issues fixed by this PR (if any):
Fixes #13067

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

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.

[gemini-code-assist]

Summary of Changes

Hello @warioddly, I'm Gemini Code Assist¹! 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 code readability and maintainability by updating a parameter name in the ArticlePage widget. The change clarifies the intent and function of the callback, making the code easier to understand for developers.

Highlights

• Parameter Renaming: Renamed the onPressed parameter to nextArticleCallback within the ArticlePage widget in listenable-builder.md for improved clarity and semantic accuracy.

🧠 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/learn/pathway/tutorial/listenable-builder.md
  • Renamed the onPressed parameter to nextArticleCallback in the ArticlePage constructor.
  • Updated the onPressed field to nextArticleCallback in the ArticlePage class definition.

Activity

• No specific activity (comments, reviews, progress) has been recorded for this pull request yet.

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. ↩

[gemini-code-assist]

Code Review

This PR correctly renames onPressed to nextArticleCallback for better clarity in the ArticlePage widget definition. However, it misses updating the call site where ArticlePage is used, which will cause the tutorial code to fail. I've left a comment with the details to fix this critical issue.

[flutter-website-bot]

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

https://flutter-docs-prod--pr13066-patch-1-3wyc10g3.web.app