fix(py): fixed broken flows in menu sample

[MengqinShen]

Fixes several broken flows in the Python menu sample and improves its usability from the Dev UI.

[gemini-code-assist]

Summary of Changes

Hello @MengqinShen, 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 the Python menu sample by fixing broken flows, standardizing naming conventions, and improving the overall developer experience. Changes include making flows more resilient to missing inputs by providing default values, refining the API key setup process, and updating the project's build configuration to better integrate with uv and genkit plugins.

Highlights

• Flow Naming Standardization: All AI flows across case_02, case_03, case_04, and case_05 have been renamed to use snake_case for consistency (e.g., s02_menuQuestion to s02_menu_question).
• Improved Flow Robustness with Default Inputs: Several flows now include default values for inputs, such as s04_indexMenuItemsFlow which uses a predefined list of menu items if none are provided, and s05_visionMenuQuestionFlow which uses a default question. Input schemas in menu_schemas.py also received default values for question and menu_text.
• Enhanced Developer Experience for API Key Setup: The GEMINI_API_KEY handling in menu_ai.py has been updated to no longer prompt the user for input. Instead, it provides a placeholder key for development UI and advises setting the environment variable for full functionality, making the sample easier to run out-of-the-box.
• Updated Build and Dependency Configuration: The pyproject.toml file has been modified to broaden the package scope for the build system and to include uv workspace sources for various genkit plugins, streamlining dependency management.

🧠 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 fixes several broken flows in the Python menu sample and improves its usability from the Dev UI. The changes include renaming flows to use snake_case for consistency, providing default values for flow inputs to allow them to run without explicit input from the Dev UI, and replacing an interactive prompt for GEMINI_API_KEY with a placeholder value. The changes are effective. My review includes suggestions to improve maintainability by extracting hardcoded data like default menu items and questions into constants. I've also noted a minor security concern regarding the hardcoded placeholder API key.