fix: Remove yiisoft/yii2-symfonymailer dependency from composer.json.

[terabytesoftw]

Q	A
Is bugfix	✔️
New feature	❌
Breaks BC	❌

Summary by CodeRabbit

• Bug Fixes

  • Removed a mailer dependency to resolve a reported issue, reducing installation requirements and potential conflicts.

• Chores

  • Simplified runtime configuration by removing default mailer setup.

• Documentation

  • Updated the changelog (version 0.1.1 Under development) to record the dependency and configuration changes (Bug fix: Remove yiisoft/yii2-symfonymailer dependency from composer.json. #146).

[coderabbitai]

Walkthrough

Removed the yiisoft/yii2-symfonymailer dependency from composer.json, deleted the mailer component and its import from config/common/components.php, and added a changelog entry under 0.1.1 (Under development) documenting the removal.

Changes

Cohort / File(s)	Summary
Dependency management composer.json	Removed yiisoft/yii2-symfonymailer (version constraint `^4.0
Configuration config/common/components.php	Removed use yii\symfonymailer\Mailer; import and deleted the mailer component configuration (previously 'mailer' => ['class' => Mailer::class, 'useFileTransport' => true]).
Documentation CHANGELOG.md	Added a bullet under version 0.1.1 (Under development) noting the removal of yiisoft/yii2-symfonymailer.

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~20 minutes

Poem

I nibbled a line from the garden of deps,
Snipped the mailer vine with gentle steps.
The changelog whispers what I did do,
Fewer seeds to tend, skies clearer and blue. 🥕✨

---

📜 Recent review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

💡 Knowledge Base configuration:

• MCP integration is disabled by default for public repositories
• Jira integration is disabled by default for public repositories
• Linear integration is disabled by default for public repositories

You can enable these sources in your CodeRabbit configuration.

📥 Commits

Reviewing files that changed from the base of the PR and between 2b63583 and 60dda75.

📒 Files selected for processing (1)

• config/common/components.php (0 hunks)

💤 Files with no reviewable changes (1)

• config/common/components.php

✨ Finishing Touches

• 📝 Generate Docstrings

🧪 Generate unit tests

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch fix-mini-55

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ 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.
  • 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.
• 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 the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

CodeRabbit Commands (Invoked using PR/Issue comments)

Type @coderabbitai help to get the list of available commands.

Other keywords and placeholders

• Add @coderabbitai ignore or @coderabbit 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

Status, Documentation and Community

• Visit our Status Page to check the current availability of CodeRabbit.
• 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.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 100.00%. Comparing base (10bae93) to head (60dda75).
⚠️ Report is 4 commits behind head on main.

Additional details and impacted files

@@             Coverage Diff             @@
##                main      #146   +/-   ##
===========================================
  Coverage     100.00%   100.00%           
  Complexity         7         7           
===========================================
  Files             12        12           
  Lines            172       172           
===========================================
  Hits             172       172           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[coderabbitai]

Actionable comments posted: 0

Caution

Some comments are outside the diff and can’t be posted inline due to platform limitations.

⚠️ Outside diff range comments (1)

composer.json (1)

13-20: Remove or replace all remaining Symfony Mailer references (or re-add the dependency)

• config/common/components.php (lines 7, 27–30): still imports yii\symfonymailer\Mailer and configures it as the mailer component
• docs/configuration.md (lines 48, 68–70): still shows use yii\symfonymailer\Mailer and a mailer config example
• composer.lock (line 8245): still locks yiisoft/yii2-symfonymailer—after updating composer.json, run composer update to regenerate the lockfile

Either remove/replace these imports and config entries (e.g. switch to a NullMailer stub) or restore the package requirement so runtime instantiation won’t fail.

🧹 Nitpick comments (1)

composer.json (1)

13-20: Optional: advertise mailer as an optional feature via Composer “suggest”.

If the app supports emailing when users choose to enable it, consider adding a Composer “suggest” entry so developers discover the package without hard requiring it.

Apply:

   "require": {
     "php": ">=8.1",
     "php-forge/foxy": "^0.1",
     "ui-awesome/html-svg":"^0.2",
     "vlucas/phpdotenv": "^5.6",
     "yiisoft/yii2": "^2.0.53|^22",
     "yiisoft/yii2-bootstrap5": "^2.0.50|^22"
   },
+  "suggest": {
+    "yiisoft/yii2-symfonymailer": "Install to enable email sending via Symfony Mailer."
+  },

📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

💡 Knowledge Base configuration:

• MCP integration is disabled by default for public repositories
• Jira integration is disabled by default for public repositories
• Linear integration is disabled by default for public repositories

You can enable these sources in your CodeRabbit configuration.

📥 Commits

Reviewing files that changed from the base of the PR and between 06d91ce and 2b63583.

⛔ Files ignored due to path filters (1)

• composer.lock is excluded by !**/*.lock

📒 Files selected for processing (2)

• CHANGELOG.md (1 hunks)
• composer.json (1 hunks)

🧰 Additional context used

🧠 Learnings (3)

📚 Learning: 2025-08-31T15:34:39.060Z

Learnt from: terabytesoftw
PR: yii2-extensions/app-basic#142
File: README.md:0-0
Timestamp: 2025-08-31T15:34:39.060Z
Learning: In yii2-extensions/app-basic project, the dev-road-runner branch is treated as the main configuration branch with no stable releases available. Static badges pointing to dev branches are intentionally used to direct users to the development version.

Applied to files:

• CHANGELOG.md

📚 Learning: 2025-08-31T15:29:19.131Z

Learnt from: terabytesoftw
PR: yii2-extensions/app-basic#142
File: docs/installation.md:21-23
Timestamp: 2025-08-31T15:29:19.131Z
Learning: In yii2-extensions/app-basic project, the composer.json file has "minimum-stability": "dev" configured, which allows Composer to install dev versions automatically without requiring --stability=dev flag in create-project commands.

Applied to files:

• composer.json

📚 Learning: 2025-07-09T14:52:41.210Z

Learnt from: terabytesoftw
PR: yii2-extensions/app-basic#97
File: docs/installation.md:5-8
Timestamp: 2025-07-09T14:52:41.210Z
Learning: The Yii2 framework has multiple active branches including the 2.0.x branch (maintenance/LTS) and the 22.0 branch (development). When specifying version requirements, "2.0.53+ or 22.x" is accurate and should not be changed to only reference the 2.x branch.

Applied to files:

• composer.json

🔇 Additional comments (1)

CHANGELOG.md (1)

7-7: Entry is clear and scoped.

Changelog line accurately documents the dependency removal under 0.1.1 (Under development). No further edits needed.