new proto annotations exist upstream

[pyramation]

This PR added amino annotations for codegen.

If we don't want to take the entire PR, I suggest we at least add this proto file

this PR in Osmosis depends on this issue

[faddat]

Okay you got it sir

[pyramation]

@faddat — can you cherry pick the annotations? I think @ValarDragon was suggesting we want to cherry pick only portions from cosmos#13501

@ValarDragon can you describe what code we do and don't want from that PR?

[faddat]

totally. I'll see what I can do rn

this?

cosmos@b49f948

[pyramation]

totally. I'll see what I can do rn

this?

cosmos@b49f948

yea that one!

[mattverse]

Agreed with just taking amino.proto from the original PR!

[pyramation]

Agreed with just taking amino.proto from the original PR!

@faddat so yea this should make it simple then ^^

[mattverse]

@pyramation Do you know if the new way of amino annotations is compatible with the current way of handling amino?

[pyramation]

@pyramation Do you know if the new way of amino annotations is compatible with the current way of handling amino?

@mattverse there are no actual changes as far as functionality or Go is concerned. However, the annotations do enable us to do many things after we have them in place!

[pyramation]

this is needed to use the new transpiler that will solve a ton of client side amino encoding for google.protobuf.Any types. Will be very useful for governance MsgSubmitProposal, as well as authz when 0.47 comes out — full amino support for any message!

Very useful also for RPC — e.g. pools and their types magically decoded!

cc @faddat @mattverse @ValarDragon

Can we open this issue back up?