Skip to content
This repository was archived by the owner on Dec 5, 2025. It is now read-only.

Add additional stats data [PFT-2543]#103

Merged
iamamitkumar0512 merged 2 commits intodevelopfrom
add-stats-data
Apr 16, 2025
Merged

Add additional stats data [PFT-2543]#103
iamamitkumar0512 merged 2 commits intodevelopfrom
add-stats-data

Conversation

@sudeepb02
Copy link
Contributor

@sudeepb02 sudeepb02 commented Apr 15, 2025

Summary by CodeRabbit

  • New Features
    • Expanded protocol statistics to include user count, settled count, position count, and referral fees received.
  • Chores
    • Updated SDK version to 2.2.16.

@coderabbitai
Copy link
Contributor

coderabbitai bot commented Apr 15, 2025

Walkthrough

This update modifies the ProtocolStats interface and the associated GraphQL query to include additional protocol metrics such as userCount, settledCount, positionCount, and referralFeesReceived. The order of several existing fields is also adjusted for both the TypeScript interface and the query. The version number in package.json is incremented from 2.2.15 to 2.2.16. No changes are made to the logic of functions or the overall structure of the code.

Changes

File(s) Change Summary
package.json Incremented version from 2.2.15 to 2.2.16.
src/subgraph/protocol/index.ts Updated ProtocolStats interface: added userCount, settledCount, positionCount, referralFeesReceived; reordered several properties.
src/subgraph/protocol/subgraphQueries.ts Modified GraphQL query in fetchProtocolTradeInfo to request new fields and reorder existing ones.

Sequence Diagram(s)

sequenceDiagram
    participant Client
    participant SDK
    participant Subgraph

    Client->>SDK: fetchProtocolTradeInfo()
    SDK->>Subgraph: GraphQL query (with new/reordered fields)
    Subgraph-->>SDK: Protocol data (userCount, settledCount, etc.)
    SDK-->>Client: ProtocolStats object (with expanded metrics)
Loading

Possibly related PRs

  • Fix Protocol Query #101: Both PRs modify the ProtocolStats interface and the GraphQL query in fetchProtocolTradeInfo by adding or reordering fields related to protocol metrics, showing a clear continuation and expansion of the same functionality.

Poem

Hopping through fields of code anew,
More stats for the protocol crew!
Users, positions, and fees now in sight,
The numbers we fetch are ever more right.
With a bump in the version, the SDK shines bright—
A rabbit’s delight on a metrics-filled night! 🐇✨

Tip

⚡💬 Agentic Chat (Pro Plan, General Availability)
  • We're introducing multi-step agentic chat in review comments and issue comments, within and outside of PR's. This feature enhances review and issue discussions with the CodeRabbit agentic chat by enabling advanced interactions, including the ability to create pull requests directly from comments and add commits to existing pull requests.

📜 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 7cf82fd and 5643244.

⛔ 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 corresponds with added protocol stats.

The version increment from 2.2.15 to 2.2.16 properly reflects the enhancement of adding new protocol metrics to the ProtocolStats interface.

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

6-14: New fields added and existing fields reordered appropriately.

The GraphQL query has been enhanced with additional protocol metrics (userCount, settledCount, positionCount, and referralFeesReceived), while maintaining the existing fields. The ordering matches the updated interface in the index.ts file.

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

5-13: Interface updated consistently with GraphQL query changes.

The ProtocolStats interface has been properly expanded to include the new metrics (userCount, settledCount, positionCount, and referralFeesReceived), and the field ordering matches the updated GraphQL query structure.

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

@sudeepb02 sudeepb02 changed the title Add additional stats data Add additional stats data [PFT-2543] Apr 15, 2025
@notion-workspace
Copy link

@iamamitkumar0512 iamamitkumar0512 merged commit a57913b into develop Apr 16, 2025
2 checks passed
@racso2609 racso2609 deleted the add-stats-data branch May 14, 2025 21:43
@racso2609 racso2609 restored the add-stats-data branch May 14, 2025 21:43
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants