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

chore: sealed_currencies v2.1.0 #297

Merged
merged 3 commits into from
Feb 8, 2025
Merged

Conversation

tsinis
Copy link
Owner

@tsinis tsinis commented Feb 8, 2025

Description

Type of Change

  • ✨ New feature (non-breaking change which adds functionality)
  • πŸ› οΈ Bug fix (non-breaking change which fixes an issue)
  • ❌ Breaking change (fix or feature that would cause existing functionality to change)
  • 🧹 Code refactor
  • πŸ§ͺ Tests
  • πŸ“ Documentation
  • βš™οΈ CI/CD or GitHub Workflow configuration change
  • πŸ“¦ Dependencies update

Checks

Please look at the following checklist to ensure that your PR can be accepted quickly:

  • Data come from open-source resources with MIT License (if presented).
  • New code is documented and the data source is referenced (if presented).
  • Existing tests are up to date with these changes.
  • New code is fully tested (if presented).

Summary by CodeRabbit

  • New Features
    β€’ Enhanced currency naming now robustly handles missing locale data for seamless integration.
    β€’ Upgraded package to version 2.1.0.

  • Documentation
    β€’ Improved API docs for currency and crypto features.
    β€’ Revised test coverage details for clarity.

  • Chores
    β€’ Streamlined internal processes with refined dependency management, removal of legacy memory tracking utilities, and optimized testing workflows.

Copy link

coderabbitai bot commented Feb 8, 2025

πŸ“ Walkthrough

Walkthrough

This pull request updates the GitHub Actions workflow by moving the Dart setup step to follow the workspace cleaning step, both controlled by the same condition. It also removes the memory tools file and the associated dependency from the sealed world tests package. In the sealed currencies package, the changelog is updated to reflect a new version and a modified method signature, the README now presents test coverage in a metric format, documentation comments in currency-related classes have been reformatted, and package version along with a dependency has been updated.

Changes

Files Change Summary
.github/workflows/verify_package_workflow.yaml Reordered steps: Workspace cleaner now executes immediately after checkout, followed by Dart setup (both conditional on is_flutter), with commented-out sections remaining unchanged.
packages/_sealed_world_tests/.../memory_tools.dart, packages/_sealed_world_tests/pubspec.yaml Deleted memory_tools.dart (which contained memory usage utilities) and removed the vm_service: ^14.2.5 dependency from the pubspec.
packages/sealed_currencies/CHANGELOG.md, README.md, .../currency/currency.dart, .../currency/submodels/crypto_currency.dart, packages/sealed_currencies/pubspec.yaml Updated changelog for version 2.1.0 with a modified maybeCommonNameFor method, revised README test coverage metrics, reformatted documentation comments in currency classes, and bumped package version and dependency (sealed_languages) to 2.1.0.

Sequence Diagram(s)

sequenceDiagram
    participant Runner as GitHub Actions Runner
    participant Checkout as Git Checkout
    participant Cleaner as Workspace Cleaner
    participant DartSetup as Dart Setup

    Runner->>Checkout: Checkout repository
    Checkout->>Cleaner: Trigger workspace cleaning (if is_flutter)
    Cleaner->>DartSetup: Proceed with Dart setup (if is_flutter)
Loading

Suggested labels

dependencies

Suggested reviewers

  • github-actions

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. (Beta)
  • @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.

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: 2

πŸ“œ Review details

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

πŸ“₯ Commits

Reviewing files that changed from the base of the PR and between 13af90f and 140ff53.

πŸ“’ Files selected for processing (8)
  • .github/workflows/verify_package_workflow.yaml (1 hunks)
  • packages/_sealed_world_tests/lib/tools/memory_tools.dart (0 hunks)
  • packages/_sealed_world_tests/pubspec.yaml (0 hunks)
  • packages/sealed_currencies/CHANGELOG.md (2 hunks)
  • packages/sealed_currencies/README.md (1 hunks)
  • packages/sealed_currencies/lib/src/model/currency/currency.dart (2 hunks)
  • packages/sealed_currencies/lib/src/model/currency/submodels/crypto_currency.dart (2 hunks)
  • packages/sealed_currencies/pubspec.yaml (2 hunks)
πŸ’€ Files with no reviewable changes (2)
  • packages/_sealed_world_tests/pubspec.yaml
  • packages/_sealed_world_tests/lib/tools/memory_tools.dart
🧰 Additional context used
πŸ““ Learnings (1)
packages/sealed_currencies/pubspec.yaml (1)
Learnt from: tsinis
PR: tsinis/sealed_world#237
File: packages/sealed_countries/pubspec.yaml:24-24
Timestamp: 2024-11-12T12:26:43.241Z
Learning: `sealed_currencies` version 1.5.1 does not introduce any breaking changes.
πŸͺ› markdownlint-cli2 (0.17.2)
packages/sealed_currencies/CHANGELOG.md

1-1: First line in a file should be a top-level heading
null

(MD041, first-line-heading, first-line-h1)

⏰ Context from checks skipped due to timeout of 90000ms (1)
  • GitHub Check: Verify sealed_currencies / ⏳ Verify sealed_currencies Package
πŸ”‡ Additional comments (7)
packages/sealed_currencies/lib/src/model/currency/submodels/crypto_currency.dart (1)

10-15: Documentation improvements look good!

The changes enhance clarity by:

  • Using consistent Markdown-style parameter references
  • Explicitly documenting optional parameters and their default values
  • Maintaining consistency with the parent Currency class documentation style

Also applies to: 47-48

packages/sealed_currencies/lib/src/model/currency/currency.dart (1)

16-22: Documentation improvements look good!

The changes enhance clarity by:

  • Using consistent Markdown-style parameter references
  • Maintaining consistent documentation style across the codebase
  • Improving readability of parameter references in class and method documentation

Also applies to: 28-29, 33-37, 73-74

packages/sealed_currencies/pubspec.yaml (2)

1-1: Version Update Confirmation
The package version has been bumped to 2.1.0. Please ensure all related documentation and tooling reflect this update.


29-29: Dependency Update Verification
The dependency for sealed_languages has been updated to ^2.1.0. Confirm that this upgrade is fully compatible with your codebase and does not introduce any breaking changes.

.github/workflows/verify_package_workflow.yaml (1)

38-43: Reordering of Dart Setup Step
The Dart setup step has been moved right after the workspace cleaner step. This reordering ensures that any workspace modifications are applied before the Dart SDK is set up. Please verify that this change preserves the intended behavior of the workflow.

packages/sealed_currencies/CHANGELOG.md (2)

1-6: Changelog Update and Refactor Details
The changelog now begins with β€œ## 2.1.0” and summarizes the refactoring of methods such as maybeCommonNameFor along with updating deprecation notices. Ensure that the instructions provided here match the accompanying migration guides and documentation.

🧰 Tools
πŸͺ› markdownlint-cli2 (0.17.2)

1-1: First line in a file should be a top-level heading
null

(MD041, first-line-heading, first-line-h1)


36-36: Deprecation Notice Clarity
The deprecation note for the sealed_currency_translations library is clear. Please double-check that the migration path to using the l10n_currencies package (or the l10n getter) is thoroughly documented for users.

Copy link

codecov bot commented Feb 8, 2025

Codecov Report

All modified and coverable lines are covered by tests βœ…

Project coverage is 100.00%. Comparing base (13af90f) to head (140ff53).
Report is 1 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff             @@
##              main      #297    +/-   ##
==========================================
  Coverage   100.00%   100.00%            
==========================================
  Files           30         7    -23     
  Lines          482       160   -322     
==========================================
- Hits           482       160   -322     
Flag Coverage Ξ”
sealed_currencies 100.00% <ΓΈ> (?)
sealed_languages ?

Flags with carried forward coverage won't be shown. Click here to find out more.

β˜” View full report in Codecov by Sentry.
πŸ“’ Have feedback on the report? Share it here.

@tsinis tsinis merged commit 4e1610d into main Feb 8, 2025
12 checks passed
@tsinis tsinis deleted the feat/sealed-currencies-v2.1.0 branch February 8, 2025 20:28
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant