docs: improve demo section in README

[koriym]

Summary

• Enhanced README demo section with console examples
• Added clear descriptions for all available demos

Changes

• Added "Console Demos" subsection with examples for:
  • Basic demo (demo/run.php)
  • Array processing demo (demo/ArrayDemo.php)
  • CSV processing demo (demo/csv/run.php)
• Restructured demo section with "Web Demo" and "Console Demos" subsections

Test plan

• All demo scripts run successfully
• README formatting is correct

🤖 Generated with Claude Code

Co-Authored-By: Claude noreply@anthropic.com

Summary by Sourcery

Enhance README’s demo section by restructuring it into separate Web and Console subsections and adding example commands for basic, array processing, and CSV demos.

Documentation:

• Restructure the Demo section into “Web Demo” and “Console Demos” subsections.
• Add console demo examples for basic, array processing, and CSV file processing commands.

Summary by CodeRabbit

• Documentation
  • Enhanced the README with clearer instructions for running demos, including new "Web Demo" and "Console Demos" sections for both browser-based and command-line examples.

[sourcery-ai]

Reviewer's Guide

Reorganized the README’s Demo section into distinct Web and Console subsections and enriched the Console Demos with clear, runnable command examples.

File-Level Changes

Change	Details	Files
Restructure demo section into Web and Console subsections	Inserted “### Web Demo” header above the existing browser launch instructions Grouped the original PHP server example under the new Web Demo subsection	README.md
Add Console Demos subsection with CLI examples	Added “### Console Demos” header Provided code block featuring commands for basic, array processing, and CSV demos	README.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!

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 README.md file was updated to include two new subsections under the Demo section: "Web Demo" and "Console Demos." These additions provide clearer, organized instructions for running demo scripts via a web server or directly from the command line.

Changes

File	Change Summary
README.md	Added "Web Demo" and "Console Demos" subsections with detailed usage instructions for each mode.

Poem

In README fields where demos grow,
Now web and console paths both show.
Run with a click, or in your shell—
Instructions clear, explained so well.
Rabbits leap with glee, you see,
For demos now are easy as can be! 🐇✨

---

📜 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 1fccdeb and 40bccb5.

📒 Files selected for processing (1)

• README.md (2 hunks)

🧰 Additional context used

🧠 Learnings (2)

📓 Common learnings

Learnt from: koriym
PR: ray-di/Ray.InputQuery#7
File: demo/csv/CsvDemo.php:0-0
Timestamp: 2025-07-06T17:00:20.164Z
Learning: When reviewing demo code, do not flag testability concerns such as using `exit` statements. The user koriym indicated that demo code should prioritize simplicity and demonstration clarity over testability improvements.

Learnt from: koriym
PR: ray-di/Ray.InputQuery#7
File: demo/csv/CsvDemo.php:96-96
Timestamp: 2025-07-06T17:00:30.839Z
Learning: When reviewing demo code, do not flag input validation or robustness concerns such as array bounds checking or malformed data handling. The user koriym indicated that demo code should prioritize simplicity and clarity, and validation warnings are unnecessary for demo purposes.

Learnt from: koriym
PR: ray-di/Ray.InputQuery#6
File: demo/multiformat/FileFormatDetector.php:53-54
Timestamp: 2025-07-05T10:38:23.505Z
Learning: When reviewing demo code, prioritize simplicity and clarity over performance optimizations. The user koriym indicated that memory optimizations are unnecessary for demo purposes, preferring straightforward implementations that are easy to understand.

Learnt from: koriym
PR: ray-di/Ray.InputQuery#6
File: demo/json/config.json:10-12
Timestamp: 2025-07-05T10:41:18.942Z
Learning: When reviewing demo code, do not flag security concerns such as hard-coded credentials. The user koriym indicated that demo code should prioritize simplicity and clarity, and security warnings are unnecessary for demo purposes.

Learnt from: koriym
PR: ray-di/Ray.InputQuery#7
File: demo/csv/CsvDemo.php:67-70
Timestamp: 2025-07-06T17:00:12.647Z
Learning: When reviewing demo code, do not flag unused parameters or suggest their removal. The user koriym indicated that demo code should prioritize simplicity and educational clarity over strict static analysis compliance, even if parameters are declared but not used in the implementation.

README.md (1)

Learnt from: CR
PR: ray-di/Ray.InputQuery#0
File: docs/CLAUDE.md:0-0
Timestamp: 2025-07-03T12:18:36.698Z
Learning: Applies to docs/src/**/*.php : Add PHPDoc for all public methods.

🔇 Additional comments (2)

README.md (2)

61-68: Clearer demo hierarchy – good improvement

Introducing the dedicated ### Web Demo heading cleanly separates web instructions from CLI usage. Nothing to add.

---

71-84: All referenced demo scripts are present

Confirmed that demo/run.php, demo/ArrayDemo.php, and demo/csv/run.php exist as specified in the README. No broken links or missing files.

---

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.

[sourcery-ai]

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

---

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