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.

Sign up for GitHub

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

Jump to bottom

how to handle the proto api v1 and v2 #135

Open
TraderWithPython opened this issue Mar 5, 2024 · 0 comments
Open

how to handle the proto api v1 and v2 #135

TraderWithPython opened this issue Mar 5, 2024 · 0 comments

Comments

@TraderWithPython
Copy link

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
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@TraderWithPython