Skip to content

feat: Require Dart 3.9#618

Open
kevmoo wants to merge 1 commit intobump_depsfrom
latest_dart
Open

feat: Require Dart 3.9#618
kevmoo wants to merge 1 commit intobump_depsfrom
latest_dart

Conversation

@kevmoo
Copy link
Collaborator

@kevmoo kevmoo commented Mar 25, 2026

Reformat code

@kevmoo kevmoo changed the base branch from main to bump_deps March 25, 2026 18:47
@kevmoo kevmoo changed the title latest dart feat: Require Dart 3.9 Mar 25, 2026
@kevmoo kevmoo requested a review from russellwheatley March 25, 2026 18:49
@kevmoo
Copy link
Collaborator Author

kevmoo commented Mar 25, 2026

This will land after #616 - that PR does the workspace bits. This is JUST formatting. Keeping things clean

@gemini-code-assist
Copy link

Summary of Changes

Hello, 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 significantly updates the project's foundational dependencies by upgrading the Dart SDK requirements and modernizing the linting setup. It streamlines configuration management and introduces various code style and safety improvements, ensuring better maintainability and adherence to current Dart best practices.

Highlights

  • Dart SDK Upgrade: The minimum Dart SDK requirement for all packages has been upgraded to Dart 3.5, and the required Dart version has been set to 3.9.0.
  • Linting Configuration Consolidation: Individual analysis_options.yaml files within packages and examples have been removed, consolidating linting rules into a single root analysis_options.yaml file. The flutter_lints package has also been updated to version ^6.0.0.
  • Code Conciseness and Robustness Improvements: Numerous code refactorings have been applied across the codebase to improve conciseness, particularly in constructor calls, widget instantiations, and callback definitions. Additionally, context.mounted checks have been introduced in several places to prevent BuildContext usage after widget disposal, enhancing application stability.

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

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
Copy link

Warning

Gemini encountered an error creating the review. You can try again by commenting /gemini review.

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.

1 participant