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

Add GRPC gateway route for listing module and add hard cap setting #2489

Merged
merged 3 commits into from
Oct 15, 2024

Conversation

shrenujb
Copy link
Contributor

@shrenujb shrenujb commented Oct 15, 2024

Changelist

Add GRPC query handler for listing module

Test Plan

[Describe how this PR was tested (if applicable)]

Author/Reviewer Checklist

  • If this PR has changes that result in a different app state given the same prior state and transaction list, manually add the state-breaking label.
  • If the PR has breaking postgres changes to the indexer add the indexer-postgres-breaking label.
  • If this PR isn't state-breaking but has changes that modify behavior in PrepareProposal or ProcessProposal, manually add the label proposal-breaking.
  • If this PR is one of many that implement a specific feature, manually label them all feature:[feature-name].
  • If you wish to for mergify-bot to automatically create a PR to backport your change to a release branch, manually add the label backport/[branch-name].
  • Manually add any of the following labels: refactor, chore, bug.

Summary by CodeRabbit

  • New Features

    • Introduced a new method, marketsHardCap, to query the hard cap number of listed markets.
    • Added an HTTP mapping for the MarketsHardCap RPC method, enabling RESTful access.
  • Bug Fixes

    • Enhanced gRPC gateway route registration with context management for improved functionality.
    • Added error handling to the registration process, addressing previous oversight.

@shrenujb shrenujb requested a review from a team as a code owner October 15, 2024 17:45
Copy link
Contributor

coderabbitai bot commented Oct 15, 2024

Walkthrough

The changes involve the addition of an import statement for the context package in the protocol/x/listing/module.go file. This update is reflected in the RegisterGRPCGatewayRoutes method of the AppModuleBasic struct, where a new context is created using context.Background(). Additionally, error handling has been incorporated into the registration process, which was previously absent. The overall structure and functionality of the AppModuleBasic and AppModule types remain unchanged. Furthermore, a new method marketsHardCap has been introduced in the LCDQueryClient class, and the MarketsHardCap RPC method in the query.proto file has been updated to include an HTTP mapping.

Changes

File Path Change Summary
protocol/x/listing/module.go Added context import; updated RegisterGRPCGatewayRoutes method to include context usage and error handling.
indexer/packages/v4-protos/src/codegen/dydxprotocol/listing/query.lcd.ts Added marketsHardCap method to LCDQueryClient; updated import statement to include new types.
proto/dydxprotocol/listing/query.proto Updated MarketsHardCap RPC method to include HTTP GET mapping to /dydxprotocol/listing/markets_hard_cap.

Possibly related PRs

  • [OTE-852] Register rpc routes in module #2480: This PR is related as it also modifies the RegisterGRPCGatewayRoutes method in a similar manner, incorporating context management and enhancing the gRPC Gateway route registration, which aligns with the changes made in the main PR.

Suggested reviewers

  • vincentwschau
  • teddyding

Poem

In the code where rabbits play,
A new context leads the way.
With error checks, we hop along,
Making sure that nothing's wrong.
Through the routes, we swiftly glide,
In our gRPC world, we take pride! 🐇✨


📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Files that changed from the base of the PR and between b1b66ec and 5a65268.

📒 Files selected for processing (1)
  • proto/dydxprotocol/listing/query.proto (1 hunks)
🚧 Files skipped from review as they are similar to previous changes (1)
  • proto/dydxprotocol/listing/query.proto

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

@shrenujb shrenujb added the pml permissionless market listing label Oct 15, 2024
Copy link
Contributor

@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

🧹 Outside diff range and nitpick comments (1)
protocol/x/listing/module.go (1)

80-83: LGTM with a suggestion: Consider more graceful error handling.

The changes improve the RegisterGRPCGatewayRoutes method by adding context and error handling. The use of context.Background() is appropriate here. However, consider a more graceful error handling approach instead of panicking, especially if this method might be called during runtime rather than just at initialization.

Consider replacing the panic with a logged error or a returned error:

if err := types.RegisterQueryHandlerClient(context.Background(), mux, types.NewQueryClient(clientCtx)); err != nil {
    // Option 1: Log the error
    log.Printf("Failed to register query handler client: %v", err)
    // Option 2: Return the error (requires changing the method signature)
    // return fmt.Errorf("failed to register query handler client: %w", err)
}

This change would make the code more robust and easier to manage in production environments.

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Files that changed from the base of the PR and between 9449952 and a6a17f8.

📒 Files selected for processing (1)
  • protocol/x/listing/module.go (2 hunks)
🧰 Additional context used
🔇 Additional comments (2)
protocol/x/listing/module.go (2)

4-4: LGTM: Context import added correctly.

The addition of the context import is appropriate for the changes made in the RegisterGRPCGatewayRoutes method.


Line range hint 1-183: Overall assessment: Changes look good with minor suggestion.

The modifications to the RegisterGRPCGatewayRoutes method successfully implement the GRPC gateway route for the listing module as intended. The addition of context and error handling improves the robustness of the code. Consider the suggestion for more graceful error handling, but otherwise, the changes are appropriate and well-implemented.

Copy link
Contributor

@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

🧹 Outside diff range and nitpick comments (1)
indexer/packages/v4-protos/src/codegen/dydxprotocol/listing/query.lcd.ts (1)

15-21: LGTM: New marketsHardCap method implemented correctly

The new marketsHardCap method has been implemented correctly. It follows the existing pattern in the class and properly utilizes the new types imported at the top of the file.

For consistency with the existing listingVaultDepositParams method, consider updating the comment style:

-  /* Queries for the hard cap number of listed markets */
+  /* Queries the hard cap number of listed markets */

This minor change would align the comment style with the existing method, improving overall code consistency.

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Files that changed from the base of the PR and between a6a17f8 and b1b66ec.

⛔ Files ignored due to path filters (2)
  • protocol/x/listing/types/query.pb.go is excluded by !**/*.pb.go
  • protocol/x/listing/types/query.pb.gw.go is excluded by !**/*.pb.gw.go
📒 Files selected for processing (2)
  • indexer/packages/v4-protos/src/codegen/dydxprotocol/listing/query.lcd.ts (2 hunks)
  • proto/dydxprotocol/listing/query.proto (1 hunks)
🧰 Additional context used
🔇 Additional comments (3)
indexer/packages/v4-protos/src/codegen/dydxprotocol/listing/query.lcd.ts (2)

2-2: LGTM: Import statement updated correctly

The import statement has been properly updated to include the new types QueryMarketsHardCap and QueryMarketsHardCapResponseSDKType. These additions are consistent with the new marketsHardCap method implementation.


12-12: LGTM: Constructor updated correctly

The constructor has been properly updated to bind the new marketsHardCap method. This is consistent with the existing pattern and ensures that the method will have the correct this context when invoked.

proto/dydxprotocol/listing/query.proto (1)

13-15: LGTM! HTTP mapping added for MarketsHardCap RPC method.

The addition of the HTTP GET mapping for the MarketsHardCap RPC method is a good improvement. It allows the method to be accessed via a RESTful HTTP endpoint, enhancing the API's accessibility and usability.

To ensure consistency and completeness, please run the following script:

Please review the output of this script to ensure that:

  1. The HTTP mapping style is consistent with other RPC methods in the listing module.
  2. Any relevant API documentation is updated to reflect this new endpoint.

@shrenujb shrenujb changed the title Add GRPC gateway route for listing module Add GRPC gateway route for listing module and add hard cap setting Oct 15, 2024
Signed-off-by: Shrenuj Bansal <[email protected]>
@shrenujb shrenujb merged commit ca15c4d into main Oct 15, 2024
39 checks passed
@shrenujb shrenujb deleted the sbansal/add_grpc_handler branch October 15, 2024 18:58
mergify bot pushed a commit that referenced this pull request Oct 15, 2024
@shrenujb
Copy link
Contributor Author

@Mergifyio backport release/protocol/v7.x

Copy link
Contributor

mergify bot commented Oct 15, 2024

backport release/protocol/v7.x

✅ Backports have been created

shrenujb added a commit that referenced this pull request Oct 15, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

Successfully merging this pull request may close these issues.

2 participants