feat: Move config fixtures into config subdirectory.

[terabytesoftw]

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

Summary by CodeRabbit

• Documentation

  • Updated the changelog to version 0.3.0 and documented the relocation of configuration fixtures.

• Tests

  • Updated test cases to use the new location for configuration fixtures.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 100.00%. Comparing base (c68c475) to head (5cc64b3).
Report is 1 commits behind head on main.

Additional details and impacted files

@@             Coverage Diff             @@
##                main       #35   +/-   ##
===========================================
  Coverage     100.00%   100.00%           
  Complexity        60        60           
===========================================
  Files              1         1           
  Lines             91        91           
===========================================
  Hits              91        91           

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

[coderabbitai]

Caution

Review failed

The pull request is closed.

Walkthrough

The changes update the changelog to reflect a new version and enhancement, specifically the relocation of configuration fixtures into a dedicated subdirectory. Correspondingly, all test references to these fixture files in the test suite were updated to use the new directory structure, with no changes to test logic or public interfaces.

Changes

Files	Change Summary
CHANGELOG.md	Updated version from 0.2.4 to 0.3.0; added entry for moving config fixtures to a config folder.
tests/ServiceMapTest.php	Updated all fixture file paths to reference the new config subdirectory.

Poem

A hop to version zero-point-three,
With fixtures tucked where they should be.
The changelog sings of order, neat,
As tests now find their config seat.
In burrows deep, our files reside,
Organized, with bunny pride! 🐇📁

---

📜 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 45277d3 and 5cc64b3.

📒 Files selected for processing (2)

• CHANGELOG.md (1 hunks)
• tests/ServiceMapTest.php (18 hunks)

✨ Finishing Touches

• 📝 Generate Docstrings

---

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

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (1)

CHANGELOG.md (1)

5-5: Add author attribution for consistency.
Previous enhancement entries include the author in parentheses. Consider updating to:

- Enh #35: Move config fixtures into `config` subdirectory (@terabytesoftw)

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 45277d3 and 5cc64b3.

📒 Files selected for processing (2)

• CHANGELOG.md (1 hunks)
• tests/ServiceMapTest.php (18 hunks)

🧰 Additional context used

🧬 Code Graph Analysis (1)

tests/ServiceMapTest.php (1)

src/ServiceMap.php (1)

• ServiceMap (63-468)

⏰ Context from checks skipped due to timeout of 90000ms (1)

• GitHub Check: phpunit-compatibility / PHP 8.3-windows-latest

🔇 Additional comments (18)

CHANGELOG.md (1)

3-3: Version header updated for upcoming release.
The new 0.3.0 Under development entry correctly precedes the dated releases.

tests/ServiceMapTest.php (17)

53-53: Approve updated fixture path for empty-container config.
Reference now includes the config subdirectory as intended.

---

62-62: Approve updated path for primary config fixture.
The config.php fixture is correctly referenced under fixture/config.

---

168-168: Approve updated fixture path for unsupported-components array test.
The path now points to fixture/config/components-unsupported-is-not-array.php.

---

182-182: Approve updated path for unsupported-components ID type test.
The fixture reference includes the new config folder.

---

203-203: Approve updated path for config unsupported return type test.
Points to fixture/config/config-unsupported-is-not-array.php.

---

217-217: Approve updated fixture path for invalid container definitions.
Now uses fixture/config/definitions-unsupported-is-not-array.php.

---

233-233: Approve updated path for invalid container type array test.
Referencing fixture/config/config-container-unsupported-type-array-invalid.php.

---

247-247: Approve updated path for invalid singletons array test.
Points to fixture/config/singletons-unsupported-is-not-array.php.

---

263-263: Approve updated path for closure definitions missing return type.
Uses fixture/config/definitions-closure-not-return-type.php.

---

277-277: Approve updated path for unsupported definition ID test.
Updated to fixture/config/definitions-unsupported-id-not-string.php.

---

291-291: Approve updated path for unsupported definition type test.
References fixture/config/definitions-unsupported-type-integer.php.

---

319-319: Approve updated path for unsupported empty-array definition test.
Now at fixture/config/definitions-unsupported-empty-array.php.

---

333-333: Approve updated path for duplicate integer definition test.
Fixture moved to fixture/config/definitions-unsupported-type-integer.php.

---

347-347: Approve updated path for singleton closure missing return type test.
Now under fixture/config/singletons-closure-not-return-type.php.

---

361-361: Approve updated path for singleton ID type test.
Points to fixture/config/singletons-unsupported-id-not-string.php.

---

375-375: Approve updated path for singleton invalid type array test.
References fixture/config/singletons-unsupported-type-array-invalid.php.

---

389-389: Approve updated path for singleton unsupported empty-array test.
Now correctly references fixture/config/singletons-unsupported-empty-array.php.