feat: gql wasm

[ruslan-sh-r]

Summary by CodeRabbit

• New Features

  • Enhanced user contract management with new default settings.
  • Expanded query capabilities for WebAssembly (Wasm) data.

• Improvements

  • Updated interval settings across various default objects for consistency.

• Documentation

  • Public interface of the query module extended to include Wasm functionality.

[coderabbitai]

Warning

Rate Limit Exceeded

@ruslan-sh-r has exceeded the limit for the number of commits or files that can be reviewed per hour. Please wait 18 minutes and 26 seconds before requesting another review.

How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.
Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.
Please see our FAQ for further information.

Commits

Files that changed from the base of the PR and between 540934b and 7ff5773.

Walkthrough

The updates focus on integrating WebAssembly (Wasm) functionality into a GraphQL system. A new type and default object for user contracts have been added, alongside the introduction of a periodInterval property to several objects. The heart of the system, the heart-monitor, now includes a method for Wasm data handling. Finally, the query module's public interface has been expanded with the addition of Wasm query exports.

Changes

File Path	Change Summary
src/indexer-nibi/defaultObjects.ts	Added GQLUserContract type and defaultUserContract; introduced periodInterval to existing constants.
src/indexer-nibi/heart-monitor.ts	Imported Wasm-related modules; added wasm method to interface and class.
src/indexer-nibi/query/index.ts	Exported ./wasm module.
src/indexer-nibi/query/wasm.ts	Created file for GraphQL Wasm data querying functionality.
src/indexer-nibi/heart-monitor.test.ts	Added tests for Wasm functionality.

Poem

🐇 "In the realm of code, where the data streams flow,
A rabbit hopped in, with Wasm in tow.
Graphs intertwine, with queries so vast,
A leap and a bound; the future's recast." 🌟

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>.
  • Generate unit-tests for this file.
• 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 tests 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 generate interesting stats about this repository from git and render them as a table.
  • @coderabbitai show all the console.log statements in this repository.
  • @coderabbitai read src/utils.ts and generate unit tests.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

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 as PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger a review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai help to get help.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

CodeRabbit Configration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• The JSON schema for the configuration file is available here.
• 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/coderabbit-overrides.v2.json

CodeRabbit Discord Community

Join our Discord Community to get help, request features, and share feedback.

[coderabbitai]

Review Status

Actionable comments generated: 1

Configuration used: CodeRabbit UI

Commits

Files that changed from the base of the PR and between 323334e and eb582f8.

Files selected for processing (4)

• src/indexer-nibi/defaultObjects.ts (9 hunks)
• src/indexer-nibi/heart-monitor.ts (4 hunks)
• src/indexer-nibi/query/index.ts (1 hunks)
• src/indexer-nibi/query/wasm.ts (1 hunks)

Files skipped from review due to trivial changes (1)

• src/indexer-nibi/query/index.ts

Additional comments: 12

src/indexer-nibi/query/wasm.ts (5)

• 1-7: The imports from ../gql/generated are correctly structured and follow the convention of importing types used within the file.
• 9-11: The QueryWasmArgs type is well-defined and aligns with the expected structure for GraphQL query arguments.
• 13-14: The GqlOutWasm interface correctly references the wasm field from the GQLQuery type, ensuring type safety for the GraphQL response.
• 17-18: The GqlWasmFields type uses a Partial wrapper, which is a good practice for optional fields in GraphQL queries.
• 58-68: The wasm function is concise and delegates the query construction to wasmQueryString and execution to doGqlQuery, which is a good separation of concerns. Ensure that doGqlQuery has proper error handling since it's an external call.

src/indexer-nibi/defaultObjects.ts (3)

• 34-34: The addition of GQLUserContract to the import list is consistent with the PR's objective to handle new data types related to Wasm.
• 186-186: The addition of the periodInterval property to various default objects is consistent with the PR's objective to expand query capabilities. Ensure that all usages of these default objects are updated to handle the new property where necessary.

Also applies to: 272-272, 281-281, 291-291, 299-299, 312-312, 331-331, 353-353

• 409-412: The defaultUserContract constant is correctly defined with the expected properties user and contractAddress, aligning with the PR's objectives.

src/indexer-nibi/heart-monitor.ts (4)

• 39-39: The import of GQLWasm is consistent with the PR's objective to handle new Wasm-related data types.
• 101-101: The imports from ./query/wasm are correctly structured and follow the convention of importing functionalities related to the Wasm queries.
• 232-235: The addition of the wasm method to the IHeartMonitor interface is consistent with the PR's objective to expand the querying capabilities of the system.
• 373-374: The implementation of the wasm method in the HeartMonitor class correctly delegates the query execution to the imported wasm function from ./query/wasm, maintaining consistency and modularity.

[github-actions]

Lines	Statements	Branches	Functions
	96.81% (6009/6207)	98.26% (679/691)	84.93% (186/219)

[coderabbitai]

Review Status

Actionable comments generated: 0

Configuration used: CodeRabbit UI

Commits

Files that changed from the base of the PR and between eb582f8 and 540934b.

Files selected for processing (1)

• src/indexer-nibi/heart-monitor.test.ts (3 hunks)

Additional comments: 2

src/indexer-nibi/heart-monitor.test.ts (2)

• 17-18: New imports QueryWasmArgs and GqlWasmFields have been added. Ensure that these are being used in the tests and that they are necessary for the new functionality.
• 1005-1040: The testWasm function has been added to test the WebAssembly functionality. Ensure that the test covers all necessary cases and that the assertions within the test are valid and meaningful. Also, verify that the defaultUserContract is correctly structured to match the expected results of the wasm function.

[cgilbe27]

See comment above