v0.2.0

[yelmuratoff]

This pull request updates documentation paths from docs/ to doc/ throughout the codebase and test suite, ensuring consistency and preventing broken links. It also refines dependency version specifications in pubspec.yaml to use caret syntax for better compatibility with future updates.

Documentation path updates:

• Changed all references in README.md from docs/ to doc/ for onboarding, validation, capabilities, migration guides, code review, and scalability documentation. [1] [2] [3] [4] [5] [6]
• Updated the code review checklist in .github/pull_request_template.md to point to doc/CODE_REVIEW.md instead of docs/CODE_REVIEW.md.
• Modified test files to reference documentation under doc/ rather than docs/, including onboarding and migration guides. [1] [2]

Dependency management:

• Updated dependencies and dev_dependencies in pubspec.yaml to use caret (^) syntax, allowing for non-breaking upgrades.

Summary by Sourcery

Standardize documentation path references and allow flexible dependency updates

Enhancements:

• Use caret syntax for dependency and dev_dependency versions in pubspec.yaml to allow non-breaking upgrades

Documentation:

• Update all documentation links and references from docs/ to doc/ across README, PR template, and codebase

Tests:

• Adjust tests to expect documentation paths under doc/ instead of docs/

[sourcery-ai]

Reviewer's Guide

This PR performs a global path migration from docs/ to doc/ for all documentation references and test validations, and refines pubspec.yaml dependency specs to use caret syntax for better forward compatibility.

Entity relationship diagram for documentation directory migration

erDiagram
    README {
      string onboardingGuide
      string validationGuide
      string capabilitiesGuide
      string migrationGuides
      string codeReviewChecklist
      string scalabilityGuide
    }
    "doc/ONBOARDING.md" ||--|| README: references
    "doc/VALIDATION.md" ||--|| README: references
    "doc/CAPABILITIES.md" ||--|| README: references
    "doc/MIGRATION_GUIDES.md" ||--|| README: references
    "doc/CODE_REVIEW.md" ||--|| README: references
    "doc/SCALABILITY.md" ||--|| README: references

    PullRequestTemplate {
      string codeReviewChecklist
    }
    "doc/CODE_REVIEW.md" ||--|| PullRequestTemplate: references

Loading

Entity relationship diagram for dependency specification update in pubspec.yaml

erDiagram
    Pubspec {
      string yaml
      string path
      string args
      string collection
      string lints
      string test
    }
    Yaml ||--|| Pubspec: dependency
    Path ||--|| Pubspec: dependency
    Args ||--|| Pubspec: dependency
    Collection ||--|| Pubspec: dependency
    Lints ||--|| Pubspec: dev_dependency
    Test ||--|| Pubspec: dev_dependency

Loading

File-Level Changes

Change	Details	Files
Normalized documentation path references from docs/ to doc/ across the repository	Replaced docs/... links with doc/... entries in README.md Updated the code review checklist in .github/pull_request_template.md Adjusted test cases to expect doc/... paths in migration and onboarding tests	README.md .github/pull_request_template.md test/docs/migration_guides_test.dart test/docs/async_logging_guidance_test.dart
Refined dependency version specifications to caret syntax	Prefixed all dependencies with ^ in pubspec.yaml Prefixed all dev_dependencies with ^ in pubspec.yaml	pubspec.yaml

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it. You can also reply to a
  review comment with @sourcery-ai issue to create an issue from it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time. You can also comment
  @sourcery-ai title on the pull request to (re-)generate the title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time exactly where you
  want it. You can also comment @sourcery-ai summary on the pull request to
  (re-)generate the summary at any time.
• Generate reviewer's guide: Comment @sourcery-ai guide on the pull
  request to (re-)generate the reviewer's guide at any time.
• Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
  pull request to resolve all Sourcery comments. Useful if you've already
  addressed all the comments and don't want to see them anymore.
• Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
  request to dismiss all existing Sourcery reviews. Especially useful if you
  want to start fresh with a new review - don't forget to comment
  @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[sourcery-ai]

Hey there - I've reviewed your changes and they look great!

---

Sourcery is free for open source - if you like our reviews please consider sharing them ✨

• X
• Mastodon
• LinkedIn
• Facebook

_{Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.}