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

[TRA-471] update shares in vault query response to use NumShares type #1834

Merged
merged 1 commit into from
Jul 2, 2024

Conversation

tqin7
Copy link
Contributor

@tqin7 tqin7 commented Jul 2, 2024

Changelist

Have total_shares in vault query response as NumShares type

Test Plan

unit testing
localnet testing

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

    • Updated the totalShares field in the Vault query responses to use a more precise custom type, improving data accuracy and consistency in vault share calculations.
  • Bug Fixes

    • Improved handling and parsing of the totalShares field to prevent potential errors related to data type conversions.
  • Tests

    • Enhanced test coverage to reflect new handling of the totalShares field, ensuring robustness and preventing future regressions.

Copy link

linear bot commented Jul 2, 2024

Copy link
Contributor

coderabbitai bot commented Jul 2, 2024

Walkthrough

The primary update involves modifying the totalShares field in the dydxprotocol/vault query and keeper logic to use a custom type NumShares instead of uint64. This change is reflected across the TypeScript, Protobuf, and Go files. The update affects both the data handling and encoding/decoding processes for the totalShares field to enhance flexibility and precision.

Changes

Files Change Summary
indexer/.../vault/query.ts Added NumShares type, made totalShares optional in QueryVaultResponse, updated related logic.
proto/.../vault/query.proto Converted total_shares field from uint64 to NumShares in QueryVaultResponse message.
protocol/x/.../grpc_query_vault.go Altered Vault function to assign totalShares directly instead of converting it to uint64.
protocol/x/.../grpc_query_vault_test.go Modified TotalShares assignment in tests using vaulttypes.BigIntToNumShares(tc.totalShares).

Sequence Diagram(s)

The changes are mainly about type updates and do not alter the control flow significantly. As such, sequence diagrams are not applicable here.

Poem

In vaults where shares do softly hum,
Types once uint64, now more wholesome,
NumShares come to take their place,
With flexibility and a smoother embrace.
Thank you, code, for growing bright,
In your changes, we delight!
🌟✨🐇

Tip

AI model upgrade

gpt-4o model for reviews and chat is now live

OpenAI claims that this model is better at understanding and generating code than the previous models. Please join our Discord Community to provide any feedback or to report any issues.


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>.
    • 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 generate interesting stats about this repository and render them as a table.
    • @coderabbitai show all the console.log statements in this repository.
    • @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 as 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.

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.
  • 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
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: 1

Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between 95e7d17 and 2ea3c4f.

Files ignored due to path filters (1)
  • protocol/x/vault/types/query.pb.go is excluded by !**/*.pb.go
Files selected for processing (4)
  • indexer/packages/v4-protos/src/codegen/dydxprotocol/vault/query.ts (7 hunks)
  • proto/dydxprotocol/vault/query.proto (1 hunks)
  • protocol/x/vault/keeper/grpc_query_vault.go (1 hunks)
  • protocol/x/vault/keeper/grpc_query_vault_test.go (1 hunks)
Additional context used
Biome
indexer/packages/v4-protos/src/codegen/dydxprotocol/vault/query.ts

[error] 9-9: An empty interface is equivalent to {}.

Safe fix: Use a type alias instead.

(lint/suspicious/noEmptyInterface)

Additional comments not posted (5)
protocol/x/vault/keeper/grpc_query_vault.go (1)

57-57: Update looks good. Ensure NumShares type is correctly handled elsewhere.

The assignment of totalShares directly to TotalShares in the QueryVaultResponse appears correct. Ensure that the NumShares type is correctly handled in other parts of the code.

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

63-63: Update looks good. Ensure NumShares type is correctly handled elsewhere.

The change of the total_shares field to the NumShares type in the QueryVaultResponse message appears correct. Ensure that the NumShares type is correctly handled in other parts of the code.

protocol/x/vault/keeper/grpc_query_vault_test.go (1)

132-132: Update looks good. Ensure NumShares type is correctly handled elsewhere.

The change to use vaulttypes.BigIntToNumShares(tc.totalShares) for the TotalShares field in the expected response appears correct. Ensure that the NumShares type is correctly handled in other parts of the code.

indexer/packages/v4-protos/src/codegen/dydxprotocol/vault/query.ts (2)

42-42: Update looks good. Ensure NumShares type is correctly handled elsewhere.

The change of the totalShares field to the NumShares type in the QueryVaultResponse interface appears correct. Ensure that the NumShares type is correctly handled in other parts of the code.


51-51: Update looks good. Ensure NumShares type is correctly handled elsewhere.

The change of the total_shares field to the NumSharesSDKType type in the QueryVaultResponseSDKType interface appears correct. Ensure that the NumSharesSDKType type is correctly handled in other parts of the code.

import { PageRequest, PageRequestSDKType, PageResponse, PageResponseSDKType } from "../../cosmos/base/query/v1beta1/pagination";
import { Params, ParamsSDKType } from "./params";
import { SubaccountId, SubaccountIdSDKType } from "../subaccounts/subaccount";
import * as _m0 from "protobufjs/minimal";
import { DeepPartial, Long } from "../../helpers";
import { DeepPartial } from "../../helpers";
/** QueryParamsRequest is a request type for the Params RPC method. */

export interface QueryParamsRequest {}
Copy link
Contributor

Choose a reason for hiding this comment

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

Avoid using empty interfaces.

An empty interface is equivalent to {}. Use a type alias instead.

- export interface QueryParamsRequest {}
+ export type QueryParamsRequest = {};
Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
export interface QueryParamsRequest {}
export type QueryParamsRequest = {};
Tools
Biome

[error] 9-9: An empty interface is equivalent to {}.

Safe fix: Use a type alias instead.

(lint/suspicious/noEmptyInterface)

@tqin7 tqin7 merged commit 4035bae into main Jul 2, 2024
33 of 34 checks passed
@tqin7 tqin7 deleted the tq/tra-471 branch July 2, 2024 19:44
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