Fix Protocol Query

[iamamitkumar0512]

Summary by CodeRabbit

• New Features

  • Added a new order count metric to protocol statistics for more comprehensive reporting.

• Chores

  • Updated the software version to 2.2.13 to incorporate the latest improvements.

[coderabbitai]

Walkthrough

This pull request bumps the package version in the package.json file from "2.2.12" to "2.2.13". In addition, it extends the protocol’s data model by adding an orderCount field. The orderCount property is incorporated into the ProtocolStats interface in the subgraph’s index.ts file and added as a field in the GraphQL query within subgraphQueries.ts. These changes augment the SDK's reporting capabilities without affecting its backward compatibility.

Changes

File(s)	Change Summary
package.json	Updated version from "2.2.12" to "2.2.13".
src/.../protocol/(index.ts, subgraphQueries.ts)	Added orderCount: a new property to the ProtocolStats interface (index.ts) and as a field in the GraphQL query (subgraphQueries.ts).

Suggested reviewers

• sudeepb02

Poem

In a garden of code, I happily play,
Adding fields and bumps in a technical ballet.
A new order count hops into our view,
With each version update shining anew.
From burrow to branch, our code sings today!

---

📜 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 4d61b1a and bc939d8.

⛔ Files ignored due to path filters (1)

• package-lock.json is excluded by !**/package-lock.json

📒 Files selected for processing (3)

• package.json (1 hunks)
• src/subgraph/protocol/index.ts (1 hunks)
• src/subgraph/protocol/subgraphQueries.ts (1 hunks)

🔇 Additional comments (3)

package.json (1)

3-3: Version bump is appropriate for adding the new field.

The version has been correctly incremented from 2.2.12 to 2.2.13, which is appropriate for a minor enhancement that maintains backward compatibility.

src/subgraph/protocol/index.ts (1)

9-9: Addition of orderCount field looks good.

The new orderCount field is properly typed as a string, which is consistent with the other count-related fields in this interface.

src/subgraph/protocol/subgraphQueries.ts (1)

10-10: GraphQL query field addition is correctly implemented.

The orderCount field has been properly added to the GraphQL query, which aligns with the interface update in index.ts.

Before merging, please verify that the GraphQL schema on the subgraph endpoint has been updated to include this field, otherwise this query might fail at runtime.

✨ 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 resolve resolve all the CodeRabbit review comments.
• @coderabbitai plan to trigger planning for file edits and PR creation.
• @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.