Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add migration guide #1189

Merged
merged 5 commits into from
Mar 2, 2025
Merged

Conversation

snapsl
Copy link
Contributor

@snapsl snapsl commented Mar 1, 2025

closes #1187

Summary by CodeRabbit

  • Documentation
    • Added a new "Migration" section to provide users with guidance on transitioning between package versions.
    • Updated the migration guide to highlight required syntax changes and revised usage practices, assisting users in adapting to the latest version.

Copy link

coderabbitai bot commented Mar 1, 2025

Warning

Rate limit exceeded

@rrousselGit has exceeded the limit for the number of commits or files that can be reviewed per hour. Please wait 22 minutes and 41 seconds before requesting another review.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

📥 Commits

Reviewing files that changed from the base of the PR and between f3da0f5 and 82b26ca.

📒 Files selected for processing (2)
  • packages/freezed/README.md (2 hunks)
  • packages/freezed/migration_guide.md (1 hunks)

Walkthrough

The pull request updates documentation for the Freezed package. A new "Migration" section is added to the README to provide a link to the migration guide and changelog. Additionally, the migration guide now details the changes necessary for upgrading from version 2 to version 3, including new requirements for class signatures, removal of auto-generated pattern matching extensions, and guidance on using classic Dart classes.

Changes

File(s) Changed Change Summary
packages/freezed/README.md Added a new "Migration" section that links to the migration guide and changelog, enhancing user navigation within the documentation.
packages/freezed/migration_guide.md Updated migration instructions for transitioning from v2 to v3 by introducing requirements for factory constructors (using sealed/abstract) and documenting the removal of .map/.when extensions in favor of Dart's native pattern matching. Also introduced the concept of "classic classes".

Suggested reviewers

  • rrousselGit

Poem

I’m just a rabbit, hopping with glee,
New docs and guides for all to see.
Migration tips to lead the way,
Code whispers changes day by day.
With every jump, we celebrate the spree!
🐇✨ Enjoy the new journey in our dev maze!


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

@snapsl
Copy link
Contributor Author

snapsl commented Mar 1, 2025

I just recognized that you can generate unions without making them sealed.

@freezed
class Union with _$Union {
  const factory Union.data(int value) = Data;
  const factory Union.loading() = Loading;
  const factory Union.error([String? message]) = Error;
}

Is there any use case to this?

@rrousselGit
Copy link
Owner

Is there any use case to this?

There's no reason to require the sealed if it works without. Folks do what they want

@snapsl
Copy link
Contributor Author

snapsl commented Mar 1, 2025

@rrousselGit Thanks for clarification.
If there are no benefits, this could lead to problems that are easily avoidable.
I would suggest to require sealed / abstract keyword here. Alternatively, a linter could be added that warns against it, but would still support this syntax.

@snapsl snapsl marked this pull request as ready for review March 1, 2025 16:37
Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 0

🧹 Nitpick comments (2)
packages/freezed/migration_guide.md (2)

35-35: Nitpick: Correct Inline Code Spacing
There is an extra space inside the inline code spans in “.map /.when”. Removing the space to read “.map/.when” will help comply with markdownlint (MD038).

🧰 Tools
🪛 markdownlint-cli2 (0.17.2)

35-35: Spaces inside code span elements
null

(MD038, no-space-in-code)


94-96: Resolve the <TODO> in Advanced Topics
The <TODO> marker indicates that the Advanced Topics section is incomplete. Please add the appropriate content or remove the placeholder to finalize the migration guide.

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 8ca2a43 and ae0d7df.

📒 Files selected for processing (2)
  • packages/freezed/README.md (2 hunks)
  • packages/freezed/migration_guide.md (1 hunks)
✅ Files skipped from review due to trivial changes (1)
  • packages/freezed/README.md
🧰 Additional context used
🪛 markdownlint-cli2 (0.17.2)
packages/freezed/migration_guide.md

35-35: Spaces inside code span elements
null

(MD038, no-space-in-code)

🔇 Additional comments (3)
packages/freezed/migration_guide.md (3)

10-22: Enforce Updated Class Signature for Person
The change from class Person with _$Person { to abstract class Person with _$Person { satisfies the new requirement for factory classes. Ensure that all usages of Person now consider its abstract status.


25-31: Enforce sealed Modifier for Model Class
Changing the declaration to sealed class Model with _$Model { is consistent with the migration guide’s requirements. This update strengthens inheritance boundaries and clarifies intent.


37-48: Adopt Dart’s Built-in Pattern Matching
The updated switch expression using pattern matching is a clear improvement over the previous .map approach. Verify that your target Dart version supports this syntax fully.

Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 0

🧹 Nitpick comments (1)
packages/freezed/migration_guide.md (1)

38-49: Adopt Dart’s Built-In Pattern Matching

Replacing the auto-generated .map extension with the Dart switch expression modernizes the code and aligns with the migration guide’s intent. It might be beneficial to explicitly mention the required Dart SDK version (e.g., Dart 3.0 or later) that supports this syntax within the guide.

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between ae0d7df and f3da0f5.

📒 Files selected for processing (1)
  • packages/freezed/migration_guide.md (1 hunks)
⏰ Context from checks skipped due to timeout of 90000ms (3)
  • GitHub Check: freezed (packages/freezed_lint, master, get)
  • GitHub Check: freezed (packages/freezed_annotation, master, get)
  • GitHub Check: freezed (packages/freezed, master, get)
🔇 Additional comments (2)
packages/freezed/migration_guide.md (2)

10-22: Update Person Class Declaration to Abstract

Changing the declaration from class Person with _$Person to abstract class Person with _$Person correctly enforces that the class cannot be directly instantiated, which aligns with the new migration requirements. Please ensure that any user code referencing Person is updated accordingly.


25-31: Enforce Sealed Hierarchy in Model Class

Updating the Model class to use the sealed keyword instead of a plain class declaration clearly restricts subtype extension to within the library. This change improves safety by ensuring the union is closed for extension and supports better exhaustiveness checking in pattern matching.

@rrousselGit
Copy link
Owner

Classes can be concrete. I cannot require abstract/sealed.

@@ -1247,6 +1248,10 @@ targets:
when_or_null: false
```
# Migration
Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This should be at the top, not the bottom

```


### Classic classes (new)
Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't see how this is related to migration

@rrousselGit rrousselGit merged commit 648412b into rrousselGit:master Mar 2, 2025
4 checks passed
@snapsl snapsl deleted the snapsl/issue1187 branch March 3, 2025 07:04
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.

Add migration guide to v3
2 participants