ci: enable all qa tools for fixtures

[martin-georgiev]

Summary by CodeRabbit

• Chores
  • Expanded static analysis, code style checks, and dependency rules to include the fixtures directory.
  • Refined test layer configuration for improved organization in dependency analysis.
  • Cleaned up unused imports in fixture files.
  • Minor formatting update by adding a newline at the end of a file.

[coderabbitai]

Walkthrough

The updates expand static analysis, code style, and dependency tracking tools to include the fixtures directory. The Deptrac configuration is restructured to introduce new layers for "Fixtures," "Integration Tests," and "Unit Tests," each with tailored rules and dependencies. The PHP CS Fixer and PHPStan configurations are modified to scan the fixtures directory. Additionally, minor cleanups are performed in the fixtures code: a newline is added to one file, and unused imports are removed from another.

Changes

File(s)	Change Summary
ci/deptrac/config.yml	Updated Deptrac configuration: added fixtures path, split "Tests" into "Fixtures," "Integration Tests," and "Unit Tests" layers, and updated rulesets accordingly.
ci/php-cs-fixer/config.php, ci/phpstan/config.neon	Added fixtures directory to PHP CS Fixer and PHPStan configuration paths.
fixtures/MartinGeorgiev/Doctrine/Entity/ContainsDecimals.php	Added a newline at the end of the file.
fixtures/MartinGeorgiev/Doctrine/Function/TestVariadicFunction.php	Removed three unused import statements.

Poem

In the garden of code, a new path appears,
Fixtures now checked, dispelling old fears.
Layers restructured, rules set anew,
Static and style tools join the review.
With imports trimmed and endings neat,
This rabbit hops on, its chores complete!
🐇✨

✨ 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.
  • 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.
• @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.

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)

ci/deptrac/config.yml (1)

33-48: Configure dependency rules for new layers.
Integration Tests depend on Fixtures, Functions, and Types; Unit Tests additionally depend on Utils. Rules align with the new layer definitions.

Optionally, review whether Unit Tests should depend on Fixtures (to avoid over-coupling test layers), depending on how fixtures are used in your unit tests.

📜 Review details

Configuration used: .coderabbit.yaml
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 2e0a1e0 and a4777a2.

📒 Files selected for processing (5)

• ci/deptrac/config.yml (2 hunks)
• ci/php-cs-fixer/config.php (1 hunks)
• ci/phpstan/config.neon (1 hunks)
• fixtures/MartinGeorgiev/Doctrine/Entity/ContainsDecimals.php (1 hunks)
• fixtures/MartinGeorgiev/Doctrine/Function/TestVariadicFunction.php (0 hunks)

💤 Files with no reviewable changes (1)

• fixtures/MartinGeorgiev/Doctrine/Function/TestVariadicFunction.php

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

• GitHub Check: PHP 8.1 + Doctrine ORM 2.14 + Doctrine Lexer 1.2
• GitHub Check: PHP 8.4 + Doctrine ORM latest + Doctrine Lexer 3.0
• GitHub Check: PHP 8.4 + Doctrine ORM latest + Doctrine Lexer latest
• GitHub Check: PHP 8.4 + Doctrine ORM 2.18 + Doctrine Lexer 2.1
• GitHub Check: PHP 8.3 + Doctrine ORM 3.0 + Doctrine Lexer latest
• GitHub Check: sloth

🔇 Additional comments (5)

fixtures/MartinGeorgiev/Doctrine/Entity/ContainsDecimals.php (1)

21-21: Skip whitespace-only change. The only addition is a newline at end of file to satisfy POSIX requirements—no functional impact.

ci/phpstan/config.neon (1)

14-17: Include fixtures in PHPStan analysis.
Adding - ../../fixtures under parameters.paths ensures your fixtures directory is now covered by PHPStan, keeping it consistent with other CI tools.

ci/php-cs-fixer/config.php (1)

11-14: Include fixtures directory in PHP CS Fixer.
The new ->in($basePath.'fixtures') call extends code style checks to your fixtures, aligning this config with PHPStan and Deptrac.

ci/deptrac/config.yml (2)

2-5: Include fixtures in Deptrac paths.
Adding - ../../fixtures under deptrac.paths ensures dependency analysis now covers your fixtures directory.

---

7-32: Define new Fixtures and Test layers.
The addition of "Fixtures", "Integration Tests", and "Unit Tests" layers introduces finer-grained dependency boundaries. Collectors correctly target:

• \Fixtures\MartinGeorgiev\.*
• \Tests\Integration\MartinGeorgiev\.*
• \Tests\Unit\MartinGeorgiev\.*
  This matches the intended namespace structure.

[coveralls]

coverage: 93.774%. remained the same
when pulling a4777a2 on more-integrations
into 2e0a1e0 on main.