Skip to content

how to handle the proto api v1 and v2 #135

Open

Description

Regarding the issue documented at cosmos/cosmos-sdk#19213, I am seeking clarity on the potential deprecation of the Proto API v1. In API v1, the utilization of custom type functions is facilitated by gogoproto, which appears not to be supported in API v2. Could you please provide guidance on how to address this limitation within API v2?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions