updating playground_component pubspec.yaml

[derrickaw]

Running into IT issues in playground on another PR, so trying to fix here.

---

Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

• Mention the appropriate issue in your description (for example: addresses #123), if applicable. This will automatically add a link to the pull request in the issue. If you would like the issue to automatically close on merging the pull request, comment fixes #<ISSUE NUMBER> instead.
• Update CHANGES.md with noteworthy changes.
• If this contribution is large, please file an Apache Individual Contributor License Agreement.

See the Contributor Guide for more tips on how to make review process smoother.

To check the build health, please visit https://github.com/apache/beam/blob/master/.test-infra/BUILD_STATUS.md

GitHub Actions Tests Status (on master branch)

See CI.md for more information about GitHub Actions CI or the workflows README to see a list of phrases to trigger workflows.

[gemini-code-assist]

Summary of Changes

Hello @derrickaw, 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 addresses and resolves internal technical issues within the playground frontend by performing a comprehensive update and pinning of several Flutter package dependencies. The changes ensure compatibility and stability across the project's various components, including generated code for assets, models, and testing utilities, which were regenerated to align with the updated dependency versions.

Highlights

• Dependency Updates and Pinning: Several Flutter package dependencies in playground_components/pubspec.yaml have been updated and explicitly pinned to specific versions (e.g., app_state, easy_localization, fluttertoast, keyed_collection_widgets, dart_style, flutter_gen_core, flutter_gen_runner). This also involved adjusting versions for intl and material_color_utilities.
• Generated Code Updates: Multiple auto-generated files have been updated. This includes playground_components/assets/symbols/go.g.yaml with numerous additions and removals of Go symbols and data structures, and playground_components/lib/src/models/example.g.dart and example_base.g.dart to include an alwaysRun field and robust contextLine parsing. Mock files (.mocks.dart) were also regenerated due to a Mockito version update.
• Asset Loading Flexibility: The provider() method in playground_components/lib/src/assets/assets.gen.dart was enhanced to accept optional bundle and package parameters, providing more control over how assets are loaded.
• Mockito Version Upgrade: The Mockito testing framework was updated from version 5.3.2 to 5.4.2 across various mock files, along with the addition of a @dart=2.19 directive in one of them.

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