refactor(exception): Move exception directory to root path directory.

[terabytesoftw]

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

Summary by CodeRabbit

• Refactor
  • Updated internal structure for exception handling to improve consistency and maintainability. No changes to user-facing functionality.
• Tests
  • Enhanced test coverage by using standardized exception messages, ensuring more reliable and descriptive test assertions.

[coderabbitai]

Walkthrough

The changes update the namespaces for exception classes and their imports from yii2\extensions\psrbridge\emitter\exception to yii2\extensions\psrbridge\exception. Additionally, test assertions now use message constants from the Message enum rather than hardcoded strings. No logic or control flow was altered.

Changes

Files/Groups	Change Summary
src/exception/HeadersAlreadySentException.php, src/exception/OutputAlreadySentException.php, src/exception/Message.php	Changed namespace from yii2\extensions\psrbridge\emitter\exception to yii2\extensions\psrbridge\exception.
src/emitter/SapiEmitter.php, tests/emitter/SapiEmitterTest.php	Updated imports for exception classes to the new namespace.
tests/emitter/SapiEmitterTest.php	Updated test assertions to use Message enum constants for exception messages.

Poem

A namespace hop, a gentle leap,
The exceptions now in folders neat.
No logic changed, just paths anew,
And tests now use the enum too!
A tidy warren, code aligned—
This rabbit’s heart is reassigned.
🐇✨

---

📜 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 8de403e and 86b2637.

📒 Files selected for processing (5)

• src/emitter/SapiEmitter.php (1 hunks)
• src/exception/HeadersAlreadySentException.php (1 hunks)
• src/exception/Message.php (1 hunks)
• src/exception/OutputAlreadySentException.php (1 hunks)
• tests/emitter/SapiEmitterTest.php (3 hunks)

🧰 Additional context used

🧠 Learnings (4)

📓 Common learnings

Learnt from: terabytesoftw
PR: yii2-extensions/psr-bridge#6
File: tests/http/RequestTest.php:1536-1552
Timestamp: 2025-07-20T16:35:15.300Z
Learning: In the yii2-extensions/psr-bridge project, the base TestCase class already handles $_SERVER cleanup in setUp() and tearDown() methods, so individual test methods that extend TestCase don't need manual $_SERVER restoration.

Learnt from: terabytesoftw
PR: yii2-extensions/psr-bridge#6
File: tests/http/RequestTest.php:1536-1552
Timestamp: 2025-07-20T16:35:15.300Z
Learning: In the yii2-extensions/psr-bridge project, the base TestCase class already handles $_SERVER cleanup in setUp() and tearDown() methods (lines 28 and 32), so individual test methods that extend TestCase don't need manual $_SERVER restoration.

Learnt from: terabytesoftw
PR: yii2-extensions/psr-bridge#6
File: tests/http/RequestTest.php:1564-1578
Timestamp: 2025-07-20T16:33:57.457Z
Learning: The TestCase class in yii2-extensions/psr-bridge automatically handles $_SERVER superglobal cleanup by saving its original state before each test and restoring it afterward in setUp() and tearDown() methods. Manual $_SERVER cleanup in individual test methods is unnecessary when extending this TestCase.

src/exception/HeadersAlreadySentException.php (2)

Learnt from: terabytesoftw
PR: yii2-extensions/psr-bridge#6
File: tests/http/RequestTest.php:1536-1552
Timestamp: 2025-07-20T16:35:15.300Z
Learning: In the yii2-extensions/psr-bridge project, the base TestCase class already handles $_SERVER cleanup in setUp() and tearDown() methods, so individual test methods that extend TestCase don't need manual $_SERVER restoration.

Learnt from: terabytesoftw
PR: yii2-extensions/psr-bridge#6
File: tests/http/RequestTest.php:1536-1552
Timestamp: 2025-07-20T16:35:15.300Z
Learning: In the yii2-extensions/psr-bridge project, the base TestCase class already handles $_SERVER cleanup in setUp() and tearDown() methods (lines 28 and 32), so individual test methods that extend TestCase don't need manual $_SERVER restoration.

src/exception/OutputAlreadySentException.php (2)

Learnt from: terabytesoftw
PR: yii2-extensions/psr-bridge#6
File: tests/http/RequestTest.php:1536-1552
Timestamp: 2025-07-20T16:35:15.300Z
Learning: In the yii2-extensions/psr-bridge project, the base TestCase class already handles $_SERVER cleanup in setUp() and tearDown() methods, so individual test methods that extend TestCase don't need manual $_SERVER restoration.

Learnt from: terabytesoftw
PR: yii2-extensions/psr-bridge#6
File: tests/http/RequestTest.php:1536-1552
Timestamp: 2025-07-20T16:35:15.300Z
Learning: In the yii2-extensions/psr-bridge project, the base TestCase class already handles $_SERVER cleanup in setUp() and tearDown() methods (lines 28 and 32), so individual test methods that extend TestCase don't need manual $_SERVER restoration.

tests/emitter/SapiEmitterTest.php (3)

Learnt from: terabytesoftw
PR: yii2-extensions/psr-bridge#6
File: tests/http/RequestTest.php:1536-1552
Timestamp: 2025-07-20T16:35:15.300Z
Learning: In the yii2-extensions/psr-bridge project, the base TestCase class already handles $_SERVER cleanup in setUp() and tearDown() methods, so individual test methods that extend TestCase don't need manual $_SERVER restoration.

Learnt from: terabytesoftw
PR: yii2-extensions/psr-bridge#6
File: tests/http/RequestTest.php:1536-1552
Timestamp: 2025-07-20T16:35:15.300Z
Learning: In the yii2-extensions/psr-bridge project, the base TestCase class already handles $_SERVER cleanup in setUp() and tearDown() methods (lines 28 and 32), so individual test methods that extend TestCase don't need manual $_SERVER restoration.

Learnt from: terabytesoftw
PR: yii2-extensions/psr-bridge#6
File: tests/http/RequestTest.php:1564-1578
Timestamp: 2025-07-20T16:33:57.457Z
Learning: The TestCase class in yii2-extensions/psr-bridge automatically handles $_SERVER superglobal cleanup by saving its original state before each test and restoring it afterward in setUp() and tearDown() methods. Manual $_SERVER cleanup in individual test methods is unnecessary when extending this TestCase.

🧬 Code Graph Analysis (2)

src/emitter/SapiEmitter.php (2)

src/exception/HeadersAlreadySentException.php (1)

• HeadersAlreadySentException (45-45)

src/exception/OutputAlreadySentException.php (1)

• OutputAlreadySentException (45-45)

tests/emitter/SapiEmitterTest.php (3)

src/exception/HeadersAlreadySentException.php (1)

• HeadersAlreadySentException (45-45)

src/exception/OutputAlreadySentException.php (1)

• OutputAlreadySentException (45-45)

src/exception/Message.php (1)

• getMessage (76-79)

🔇 Additional comments (7)

src/exception/Message.php (1)

5-5: LGTM! Namespace reorganization improves accessibility.

The namespace change from yii2\extensions\psrbridge\emitter\exception to yii2\extensions\psrbridge\exception is appropriate and aligns with the PR objective. This makes the Message enum more accessible to other components beyond just the emitter.

src/emitter/SapiEmitter.php (1)

9-9: LGTM! Import statement correctly updated for new namespace.

The import statement has been properly updated to reflect the new exception namespace structure. All exception classes are now imported from yii2\extensions\psrbridge\exception which is consistent with the namespace reorganization.

src/exception/HeadersAlreadySentException.php (1)

5-5: LGTM! Consistent namespace reorganization.

The namespace change from yii2\extensions\psrbridge\emitter\exception to yii2\extensions\psrbridge\exception is consistent with the overall refactoring effort and maintains the class functionality intact.

src/exception/OutputAlreadySentException.php (1)

5-5: LGTM! Namespace change maintains consistency.

The namespace update from yii2\extensions\psrbridge\emitter\exception to yii2\extensions\psrbridge\exception is consistent with the other exception classes and properly implements the namespace reorganization.

tests/emitter/SapiEmitterTest.php (3)

13-13: LGTM! Import statement properly updated.

The import statement has been correctly updated to use the new exception namespace yii2\extensions\psrbridge\exception, maintaining consistency with the namespace reorganization.

---

685-685: LGTM! Improved test maintainability with enum usage.

The exception message assertion now uses Message::UNABLE_TO_EMIT_RESPONSE_HEADERS_ALREADY_SENT->getMessage() instead of a hardcoded string. This improves maintainability by centralizing message definitions and ensures consistency with the Message enum implementation.

---

703-703: LGTM! Consistent enum usage for exception messages.

The exception message assertion properly uses Message::UNABLE_TO_EMIT_OUTPUT_HAS_BEEN_EMITTED->getMessage() instead of a hardcoded string. This change maintains consistency with other test methods and leverages the centralized message management provided by the Message enum.

✨ Finishing Touches

• 📝 Generate Docstrings

---

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.
  • Explain this complex logic.
  • 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 explain this code block.
  • @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 explain its main purpose.
  • @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.

Support

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

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 generate sequence diagram to generate a sequence diagram of the changes in 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.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 100.00%. Comparing base (8de403e) to head (86b2637).
Report is 1 commits behind head on main.

Additional details and impacted files

@@             Coverage Diff             @@
##                main        #8   +/-   ##
===========================================
  Coverage     100.00%   100.00%           
  Complexity       100       100           
===========================================
  Files              6         6           
  Lines            257       257           
===========================================
  Hits             257       257           

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