Support Dart 3.6.0 and analyzer 6.9.0 as a minimum.

[davidmartos96]

Was there any reason for limiting the analyzer dependency to v7 and Dart to 3.7 ?
The freezed core dependencies such as source gen support analyzer 6.9.0 and Dart 3.6.

I tried running the tests and examples in Flutter 3.27 (Dart 3.6) and everything works great. (I had to locally patch these changes though, as it appears the example is not up to date) #1183

Summary by CodeRabbit

• Chores
  • Updated minimum supported versions for Dart (now 3.6.0) and the analyzer (now 6.9.0) to broaden compatibility.
  • Adjusted dependency constraints to support a wider range of environments.
• Documentation
  • Enhanced configuration guidance to clarify how formatting settings for generated files work when using newer Dart SDK versions.
• Bug Fixes
  • Removed optional parameters from the constructors of the Complex class for simplification.
• Style
  • Improved code readability across various files through consistent formatting adjustments.

[coderabbitai]

Walkthrough

The changes update version requirements and documentation for the freezed package. The changelog now reflects that Dart 3.6.0 and analyzer 6.9.0 are the minimum requirements. The SDK constraint and analyzer dependency in the pubspec.yaml file have been adjusted accordingly. Additionally, the README.md now includes clarifying comments in the build.yaml configuration section regarding the applicability of disabling formatting for .freezed.dart files.

Changes

File(s)	Change summary
packages/freezed/CHANGELOG.md, packages/freezed/pubspec.yaml	Updated version requirements: changelog now notes Dart 3.6.0 and analyzer 6.9.0, and pubspec.yaml’s SDK constraint and analyzer dependency have been revised to match these versions.
packages/freezed/README.md	Added comments in the build.yaml section clarifying that disabling formatting for .freezed.dart files applies only when the project opts into Dart 3.7 or higher in its SDK constraints.

Suggested reviewers

• rrousselGit

Poem

I'm a hopping rabbit with a code-filled cheer,
Dart and analyzer updated—now everything's clear.
Changelog, pubspec, and README in line,
Each update a small hop to keep our code divine.
With gentle leaps and lines of code so bright,
I celebrate these changes from morning till night.
🐇✨

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 5569143 and 2356d00.

📒 Files selected for processing (1)

• packages/freezed/CHANGELOG.md (1 hunks)

🚧 Files skipped from review as they are similar to previous changes (1)

• packages/freezed/CHANGELOG.md

⏰ Context from checks skipped due to timeout of 90000ms (3)

• GitHub Check: freezed (packages/freezed, master, get)
• GitHub Check: freezed (packages/freezed_lint, master, get)
• GitHub Check: freezed (packages/freezed_annotation, master, get)

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[rrousselGit]

Dart 3.7 is needed for // dart format off in generated code.

[davidmartos96]

I see. Would it be possible to simply document that the "no-format" option is only available when opting into Dart 3.7?

Given the controversy on the new formatter rules, I believe there will be some folks that won't opt into Dart 3.7 for a while. And if freezed can work in a 99% of its features with 3.6, I think it would be worth the change.

[rrousselGit]

Fair. Do you mind documenting it?

[davidmartos96]

@rrousselGit Done. Is it ok in the README?

[rrousselGit]

Sounds good. Do you mind fixing the CI?

[davidmartos96]

@rrousselGit How should we fix it? Go back to the 3.6 formatter and reformat the whole source code? The new format only runs when targeting 3.7 as a minimum

[rrousselGit]

Sure. Whatever makes the CI happy, I don't care

[davidmartos96]

Is there anything else you think should be done here? @rrousselGit

[rrousselGit]

LGTM thanks!