cosmos-proto icon indicating copy to clipboard operation
cosmos-proto copied to clipboard

Results 23 cosmos-proto issues
Sort by recently updated
recently updated
newest added

Bumps google.golang.org/protobuf from 1.34.0 to 1.34.1. [![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=google.golang.org/protobuf&package-manager=go_modules&previous-version=1.34.0&new-version=1.34.1)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a...

dependencies

Regarding the issue documented at https://github.com/cosmos/cosmos-sdk/issues/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...

CC @tac0turtle @aaronc @odeke-em

* `cosmos_proto.scalar` proto option that applies `string` and `bytes` types * Mapping YAML config file between scalars (language agnostic) and golang types Ex: ```yaml scalars: cosmos.Int: github.com/cosmos/cosmos-sdk/types.Int ``` * define...

WG: Framework

Probably the only things that really need to be exposed are in `runtime` and the `cosmos_proto.proto` extensions.

WG: Framework

Hi. I hope you are having a great new year so far. Is there documentation on how to use this library? Someone recommended I consider it for a project we...

Work in progress for pulsar 1.0, so far fixing #50 and #37. Builds upon #108 to avoid merge conflicts while it's in review. @aaronc @tac0turtle in light of https://github.com/cosmos/cosmos-proto/issues/2#issuecomment-1483558053, is...

The ProtoMethods is called for every unmarshal, which in turn allocates an protoiface.Methods. The Methods object does not refer to a partucular message object, so the allocation can be saved...

## Summary Write a new utililty function that's the same as `dynamicpb.NewMessageType`, but when a nested field is a known type, use that resolved type, instead of a new dynamicpb.Message....

enhancement