fix: disable product indexing checker hint for versions <6.6.10.5

[schneider-felix]

Summary by CodeRabbit

• Bug Fixes
  • Disabled the product stream indexing health check for Shopware versions older than 6.6.10.5 to prevent incorrect or unnecessary alerts on unsupported versions.

[coderabbitai]

Walkthrough

The ProductStreamIndexingChecker class was updated to accept the current Shopware version as a constructor parameter. The collect method now checks the Shopware version and exits early if it is below 6.6.10.5, disabling the health check for older versions.

Changes

File(s)	Change Summary
src/Components/Health/Checker/PerformanceChecker/ProductStreamIndexingChecker.php	Added Shopware version as constructor parameter; collect method now checks version and exits early for versions < 6.6.10.5.

Sequence Diagram(s)

sequenceDiagram
    participant Caller
    participant ProductStreamIndexingChecker

    Caller->>ProductStreamIndexingChecker: construct(shopwareVersion)
    Caller->>ProductStreamIndexingChecker: collect()
    ProductStreamIndexingChecker->>ProductStreamIndexingChecker: check shopwareVersion
    alt shopwareVersion < 6.6.10.5
        ProductStreamIndexingChecker-->>Caller: return (no results)
    else shopwareVersion >= 6.6.10.5
        ProductStreamIndexingChecker->>ProductStreamIndexingChecker: proceed with health check
        ProductStreamIndexingChecker-->>Caller: return results
    end

Loading

Poem

A version check now guards the stream,
For Shopware old, we halt the dream.
Only newer shops may peek,
At health results they seek.
With a hop and a check, we bound ahead—
🐇 Keeping code healthy, just as we said!

---

📜 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 f9e6857 and 590aaeb.

📒 Files selected for processing (1)

• src/Components/Health/Checker/PerformanceChecker/ProductStreamIndexingChecker.php (1 hunks)

🚧 Files skipped from review as they are similar to previous changes (1)

• src/Components/Health/Checker/PerformanceChecker/ProductStreamIndexingChecker.php

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

[coderabbitai]

Actionable comments posted: 2

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between aad1adc and f9e6857.

📒 Files selected for processing (1)

• src/Components/Health/Checker/PerformanceChecker/ProductStreamIndexingChecker.php (2 hunks)

🧰 Additional context used

🧬 Code Graph Analysis (1)

src/Components/Health/Checker/PerformanceChecker/ProductStreamIndexingChecker.php (5)

src/Components/Health/Checker/HealthChecker/ProductionChecker.php (1)

• collect (20-29)

src/Components/Health/Checker/PerformanceChecker/CompressionMethodChecker.php (1)

• collect (28-36)

src/Components/Health/Checker/PerformanceChecker/FixCacheIdSetChecker.php (1)

• collect (21-40)

src/Components/Health/Checker/PerformanceChecker/FineGrainedCachingChecker.php (1)

• collect (26-44)

src/Components/Health/HealthCollection.php (1)

• HealthCollection (12-18)

🔇 Additional comments (1)

src/Components/Health/Checker/PerformanceChecker/ProductStreamIndexingChecker.php (1)

18-19: LGTM! Constructor parameter addition follows established patterns.

The addition of the Shopware version parameter with proper dependency injection follows the same pattern used in other performance checkers.

[coderabbitai]

🛠️ Refactor suggestion

Consider using PHP's native version_compare for consistency.

While the Composer Semver library works correctly, other performance checkers in the codebase use PHP's native version_compare function for version checks. This creates an inconsistency in the codebase.

For consistency with existing patterns, consider removing this import and using version_compare instead:

-use Composer\Semver\Semver;

Committable suggestion skipped: line range outside the PR's diff.

🤖 Prompt for AI Agents

In
src/Components/Health/Checker/PerformanceChecker/ProductStreamIndexingChecker.php
at line 7, remove the import statement for Composer\Semver\Semver and replace
any usage of Semver for version comparisons with PHP's native version_compare
function to maintain consistency with other performance checkers in the
codebase.