docs: fix sample code in Injecting Providers

[tenkoma]

Removed unnecessary char.

Summary by Sourcery

Documentation:

• Fix PHP sample code in the Injecting Providers section.

Summary by CodeRabbit

• Documentation
  • Refined dependency injection guides with improved clarity in code examples.
  • Aligned the presentation of technical instructions across language versions for consistent user reference.

[sourcery-ai]

Reviewer's Guide by Sourcery

This pull request removes an unnecessary character from the sample code in the Injecting Providers documentation. The character was causing a syntax error in the code snippet.

Updated class diagram for LogFileTransactionLog

classDiagram
  class LogFileTransactionLog {
    -ProviderInterface $connectionProvider
    +__construct(ProviderInterface $connectionProvider)
    +logChargeResult(ChargeResult $result)
  }

Loading

File-Level Changes

Change	Details	Files
Removed an unnecessary character from the sample code in the Injecting Providers documentation.	Removed an unnecessary parenthesis from the sample code.	manuals/1.0/en/170.InjectingProviders.md manuals/1.0/ja/170.InjectingProviders.md

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it. You can also reply to a
  review comment with @sourcery-ai issue to create an issue from it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time. You can also comment
  @sourcery-ai title on the pull request to (re-)generate the title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time exactly where you
  want it. You can also comment @sourcery-ai summary on the pull request to
  (re-)generate the summary at any time.
• Generate reviewer's guide: Comment @sourcery-ai guide on the pull
  request to (re-)generate the reviewer's guide at any time.
• Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
  pull request to resolve all Sourcery comments. Useful if you've already
  addressed all the comments and don't want to see them anymore.
• Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
  request to dismiss all existing Sourcery reviews. Especially useful if you
  want to start fresh with a new review - don't forget to comment
  @sourcery-ai review to trigger a new review!
• Generate a plan of action for an issue: Comment @sourcery-ai plan on
  an issue to generate a plan of action for it.

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[coderabbitai]

Walkthrough

The changes modify the constructor of the LogFileTransactionLog class by removing parentheses around the #[Set(Connection::class)] attribute used for dependency injection. Additionally, in the Japanese version, the logChargeResult method is updated to correctly access the connectionProvider when a charge result indicates failure. These adjustments improve the code’s clarity without modifying its overall functionality.

Changes

Files	Change Summary
manuals/1.0/en/170.InjectingProviders.md manuals/1.0/ja/170.InjectingProviders.md	Constructor signature updated by removing unnecessary parentheses around the attribute #[Set(Connection::class)].
manuals/1.0/ja/170.InjectingProviders.md	logChargeResult method modified to correctly access connectionProvider when handling a failure charge result.

Sequence Diagram(s)

sequenceDiagram
    participant Client
    participant LogFileTransactionLog
    participant ConnectionProvider

    Client->>LogFileTransactionLog: logChargeResult(chargeResult)
    alt chargeResult indicates failure
      LogFileTransactionLog->>ConnectionProvider: getConnection()
      ConnectionProvider-->>LogFileTransactionLog: connection
    else success
      LogFileTransactionLog-->>Client: no provider call
    end

Loading

Poem

In the code forest where bugs once did hide,
I hop through changes with a joyful stride.
Constructors gleam without extra flair,
And methods check failures with care.
With twitching whiskers and digital delight,
I celebrate clean code from morning to night! 🐰💻

---

📜 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 e87d542 and 75260f4.

📒 Files selected for processing (2)

• manuals/1.0/en/170.InjectingProviders.md (1 hunks)
• manuals/1.0/ja/170.InjectingProviders.md (1 hunks)

✅ Files skipped from review due to trivial changes (1)

• manuals/1.0/en/170.InjectingProviders.md

🔇 Additional comments (2)

manuals/1.0/ja/170.InjectingProviders.md (2)

87-87: LGTM! Improved attribute syntax.

The removal of unnecessary parentheses around the attribute improves code clarity and aligns with PHP 8 attribute syntax best practices.

---

93-93: Inconsistency with AI summary.

The AI summary mentioned changes to the logChargeResult method's access to connectionProvider, but no such changes are marked in the provided code.

Likely an incorrect or invalid review comment.

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ 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. (Beta)
• @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.

[sourcery-ai]

Hey @tenkoma - I've reviewed your changes and they look great!

Here's what I looked at during the review

• 🟢 General issues: all looks good
• 🟢 Security: all looks good
• 🟢 Testing: all looks good
• 🟢 Complexity: all looks good
• 🟢 Documentation: all looks good

---

Sourcery is free for open source - if you like our reviews please consider sharing them ✨

• X
• Mastodon
• LinkedIn
• Facebook

_{Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.}