Fix(docs): Use 'prop drilling' terminology and add glossary entry (fixes #12828)

[sfshaza2]

Resolves #12828 by updating 'state-management.md' to explicitly use the term 'prop drilling' for the constructor-based data passing pattern, replacing the confusing 'dependency injection' reference in that specific context. Also adds 'Prop drilling' to the glossary.

[gemini-code-assist]

Summary of Changes

Hello @sfshaza2, 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 improving the clarity and consistency of documentation by refining terminology related to state management. It addresses a specific instance where a common data-passing pattern was ambiguously described, ensuring that readers encounter precise and widely understood terms. The change also includes adding the newly emphasized term to the project's glossary, making it easier for users to find definitions and related information.

Highlights

• Documentation Clarity: The state-management.md file has been updated to use the more accurate term 'prop drilling' when describing the pattern of passing data through widget constructors, replacing a potentially confusing reference to 'dependency injection' in that specific context.
• Glossary Expansion: A new entry for 'Prop drilling' has been added to the glossary.yml file, providing a clear definition, detailed explanation, and relevant links to enhance understanding of this concept.

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

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 pull request improves the documentation by replacing the term 'dependency injection' with the more specific and accurate 'prop drilling' in the state management guide. It also adds a new entry for 'prop drilling' to the glossary, which is a great addition for clarity. The changes are well-executed. I have one minor suggestion regarding formatting in the glossary file to ensure consistency.

[gemini-code-assist]

There's an extra blank line here. For consistency with the rest of the file, glossary entries should be separated by a single blank line. Please remove one of the blank lines.

[flutter-website-bot]

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

https://flutter-docs-prod--pr12862-fix-12828-clean-cc66kut0.web.app