fix read only query builder

[barakb]

Fix clippy warnings
Update version on readme

Summary by CodeRabbit

• New Features

  • Updated version number for falkordb crate to 0.1.10 in documentation.

• Documentation

  • Improved clarity and formatting of documentation comments across various methods.
  • Expanded documentation for the with_timeout method in QueryBuilder.

• Bug Fixes

  • Simplified control flow in the parse_string_array function by removing unnecessary iterations.

• Refactor

  • Adjusted lifetime parameters in LazyResultSet for improved flexibility.
  • Updated command strings for read-only queries to align with new naming conventions in multiple components.
  • Simplified implementation of QueryBuilder and ProcedureQueryBuilder by removing explicit lifetime annotations.

[coderabbitai]

Walkthrough

The changes in this pull request primarily consist of version updates for the falkordb crate from 0.1.9 to 0.1.10 in the README.md file, ensuring consistency across installation instructions and feature enablement examples. Additionally, several modifications were made to the documentation and implementation of methods in various source files, focusing on formatting improvements and minor adjustments to command strings for read-only queries in the AsyncGraph and SyncGraph structs. The overall functionality and logic of the code remain unchanged.

Changes

File	Change Summary
README.md	Updated version number from 0.1.9 to 0.1.10 in multiple sections including installation and features.
src/client/blocking.rs	Adjusted documentation comments for connection_pool_size and config_get methods for consistency. borrow_connection method updated to call FalkorSyncClientInner.
src/graph/asynchronous.rs	Changed constant in ro_query method from "GRAPH.QUERY_RO" to "GRAPH.RO_QUERY".
src/graph/blocking.rs	Changed command string in ro_query method from "GRAPH.QUERY_RO" to "GRAPH.RO_QUERY".
src/graph/query_builder.rs	Updated with_timeout documentation, changed command string in common_execute_steps, and simplified lifetime annotations in impl blocks.
src/response/index.rs	Removed unnecessary into_iter() call in parse_string_array function for simplification.
src/response/lazy_result_set.rs	Changed lifetime parameter in LazyResultSet from <'a> to '_ in the Iterator implementation.
Cargo.toml	Updated thiserror dependency version from 2.0.4 to 2.0.6.

Possibly related PRs

• Fix async connection leak and co #72: This PR updates the version number in the README.md file from 0.1.8 to 0.1.9, which is related to the main PR that updates the version from 0.1.9 to 0.1.10.
• add support with the new vec32 #48: This PR modifies the README.md file, updating code examples to reflect changes in method calls and data handling, which may relate to the overall documentation consistency being addressed in the main PR.
• Update dependencies #66: This PR updates the thiserror dependency version in Cargo.toml, which is relevant as the main PR also includes a version update for a dependency in Cargo.toml.
• Update dependecies #74: Similar to Update dependencies #66, this PR updates the thiserror dependency version in Cargo.toml, which aligns with the changes made in the main PR regarding dependency version updates.

Suggested reviewers

• gkorland
• AviAvni

Poem

In the code where rabbits play,
A version change brightens the day.
From nine to ten, we hop along,
With queries fixed, we sing our song.
Documentation clear, no need to fret,
In the land of Falkor, no regrets! 🐇✨

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Reviewing files that changed from the base of the PR and between 95ea43e and 4cf09a7.

📒 Files selected for processing (1)

• src/client/blocking.rs (4 hunks)

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

• src/client/blocking.rs

---

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. (Experiment)
• @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.

[codecov]

Codecov Report

Attention: Patch coverage is 81.81818% with 6 lines in your changes missing coverage. Please review.

Project coverage is 85.29%. Comparing base (403e899) to head (4cf09a7).
Report is 1 commits behind head on main.

Files with missing lines	Patch %	Lines
src/client/blocking.rs	89.65%	3 Missing ⚠️
src/graph/query_builder.rs	0.00%	2 Missing ⚠️
src/graph/asynchronous.rs	0.00%	1 Missing ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##             main      #77      +/-   ##
==========================================
+ Coverage   85.11%   85.29%   +0.18%     
==========================================
  Files          28       28              
  Lines        3910     3938      +28     
  Branches     3910     3938      +28     
==========================================
+ Hits         3328     3359      +31     
+ Misses        390      387       -3     
  Partials      192      192              

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[coderabbitai]

Actionable comments posted: 0

🧹 Outside diff range and nitpick comments (1)

Cargo.toml (1)

Version mismatch confirmed between Cargo.toml (0.1.9) and README.md (0.1.10)

The version inconsistency has been verified:

• Cargo.toml specifies version "0.1.9"
• README.md consistently references version "0.1.10" across multiple dependency declarations

Please update the version in Cargo.toml to "0.1.10" to maintain consistency with README.md.

🔗 Analysis chain

Line range hint 1-24: Version mismatch between Cargo.toml and README.md

The package version in Cargo.toml is still at "0.1.9", but according to the AI summary, README.md has been updated to "0.1.10". Please ensure version numbers are consistent across all files.

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Verify version consistency across files
echo "Version in Cargo.toml:"
rg -A 1 'version = "0.1' Cargo.toml

echo -e "\nVersion in README.md:"
rg 'falkordb = \{ version = "0.1' README.md

Length of output: 925

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Reviewing files that changed from the base of the PR and between d4789e7 and 8bd6cf5.

⛔ Files ignored due to path filters (1)

• Cargo.lock is excluded by !**/*.lock

📒 Files selected for processing (2)

• Cargo.toml (1 hunks)
• src/client/blocking.rs (3 hunks)

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

• src/client/blocking.rs

🔇 Additional comments (1)

Cargo.toml (1)

23-23: LGTM: Safe dependency version bump

The update of thiserror from 2.0.4 to 2.0.6 is a minor version bump that follows semantic versioning principles.