Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat: add getControllers and update subscription functions #396

Merged
merged 1 commit into from
Feb 13, 2025

Conversation

MartianGreed
Copy link
Collaborator

@MartianGreed MartianGreed commented Feb 13, 2025

Closes #

Introduced changes

Checklist

  • Linked relevant issue
  • Updated relevant documentation
  • Added relevant tests
  • Add a dedicated CI job for new examples
  • Performed self-review of the code

Summary by CodeRabbit

  • New Features
    • Introduced asynchronous methods to update both entity and event subscriptions with configurable filtering options.
    • Enabled the option to include historical data when updating event message subscriptions.
    • Added a feature to retrieve controller information based on specified contract addresses.

Copy link

coderabbitai bot commented Feb 13, 2025

Walkthrough

This PR introduces three new asynchronous methods into the SDK. The methods, updateEntitySubscription, updateEventMessageSubscription, and getControllers, expand the API to support updating subscription information and retrieving controller data. These changes are reflected in both the core implementation (index file) and the public SDK interface (types file), ensuring consistency across usage and type definitions.

Changes

File(s) Change Summary
packages/sdk/.../index.ts, packages/sdk/.../types.ts Added new async methods: updateEntitySubscription(subscription, clauses), updateEventMessageSubscription(subscription, clauses, historical), and getControllers(contract_addresses). These methods allow updating subscriptions (with optional historical processing) and fetching controllers by contract addresses.

Sequence Diagram(s)

sequenceDiagram
    participant Client
    participant SDK
    participant SubscriptionService
    Client->>SDK: updateEntitySubscription(subscription, clauses)
    SDK->>SubscriptionService: Process Update Request
    SubscriptionService-->>SDK: Confirmation
    SDK-->>Client: Promise Resolved
Loading
sequenceDiagram
    participant Client
    participant SDK
    participant MessageService
    Client->>SDK: updateEventMessageSubscription(subscription, clauses, historical)
    SDK->>MessageService: Process Event Message Update
    MessageService-->>SDK: Confirmation
    SDK-->>Client: Promise Resolved
Loading
sequenceDiagram
    participant Client
    participant SDK
    participant ControllerService
    Client->>SDK: getControllers(contract_addresses)
    SDK->>ControllerService: Request Controllers Data
    ControllerService-->>SDK: Returns Controllers
    SDK-->>Client: Promise Resolved with Data
Loading

Possibly related PRs

Poem

I'm a rabbit, hopping through the code so fine,
New methods here make my circuits shine.
Subscriptions update with a joyful leap,
Controllers join in, no promises to keep.
Hooray for neat code and a structure so grand—
Happy binkies and bytes all over the land!

✨ Finishing Touches
  • 📝 Generate Docstrings (Beta)

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

Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 0

🧹 Nitpick comments (3)
packages/sdk/src/index.ts (3)

331-347: Consider adding error handling.

While the implementation is correct, consider adding try-catch block to handle potential errors from the client method and provide more context-specific error messages.

 updateEntitySubscription: async (
     subscription: torii.Subscription,
     clauses: torii.EntityKeysClause[]
 ): Promise<void> => {
+    try {
         return await client.updateEntitySubscription(subscription, clauses);
+    } catch (error) {
+        throw new Error(`Failed to update entity subscription: ${error.message}`);
+    }
 },

349-371: Add parameter validation for historical flag.

Consider validating the historical parameter to ensure it's a boolean value.

 updateEventMessageSubscription: async (
     subscription: torii.Subscription,
     clauses: torii.EntityKeysClause[],
     historical: boolean
 ): Promise<void> => {
+    if (typeof historical !== 'boolean') {
+        throw new TypeError('historical parameter must be a boolean');
+    }
     return await client.updateEventMessageSubscription(
         subscription,
         clauses,
         historical
     );
 },

373-388: Validate contract addresses format.

Consider adding validation for contract addresses to ensure they are valid hex strings.

 getControllers: async (
     contract_addresses: string[]
 ): Promise<torii.Controllers> => {
+    const isValidHexString = (str: string) => /^0x[0-9a-fA-F]+$/.test(str);
+    const invalidAddresses = contract_addresses.filter(addr => !isValidHexString(addr));
+    if (invalidAddresses.length > 0) {
+        throw new Error(`Invalid hex format for addresses: ${invalidAddresses.join(', ')}`);
+    }
     return await client.getControllers(contract_addresses);
 },
📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between f06a3b8 and 0bad2fb.

📒 Files selected for processing (2)
  • packages/sdk/src/index.ts (1 hunks)
  • packages/sdk/src/types.ts (1 hunks)
⏰ Context from checks skipped due to timeout of 90000ms (2)
  • GitHub Check: check
  • GitHub Check: build
🔇 Additional comments (3)
packages/sdk/src/types.ts (3)

382-396: LGTM!

The interface definition is well-documented and correctly typed.


398-414: LGTM!

The interface definition is well-documented and correctly typed.


416-429: LGTM!

The interface definition is well-documented and correctly typed.

@MartianGreed MartianGreed merged commit af2e457 into main Feb 13, 2025
6 checks passed
@MartianGreed MartianGreed deleted the feat/add-sdk-functions branch February 13, 2025 19:29
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant