some accepts/implements annotations don't resolve to existing scopes #14353
Closed
Description
I've gone over every accepts/implements interface and found some discrepancies.
I've parsed the accepts
and implements
and analyzed every possible lookups that the Go interpreter will lookup based on the .proto and the name used in the annotation (link to the Go protobuf scope lookup algorithm)
If I misunderstood something, please let me know!
Here are the bad protos that I've found
cosmos/bank/v1beta1/authz.proto
(SendAuthorization
)
Required scope:cosmos.authz.Authorization
Possible lookup scopes:
cosmos.bank.v1beta1.Authorization
cosmos.bank.Authorization
cosmos.Authorization
Authorization
cosmos/gov/v1/tx.proto
(MsgExecLegacyContent
)
Required scope:cosmos.gov.v1beta1.Content
? (does v1 point to v1beta1 Content interface?)
Possible lookup scopes:
cosmos.gov.v1.Content
cosmos.gov.Content
cosmos.Content
Content
cosmos/group/v1/tx.proto
(MsgCreateGroupPolicy
,MsgCreateGroupWithPolicy
,MsgUpdateGroupPolicyDecisionPolicy
)
Required scope:cosmos.group.DecisionPolicy
Possible lookup scopes:
cosmos.group.v1.cosmos.group.v1.DecisionPolicy
cosmos.group.cosmos.group.v1.DecisionPolicy
cosmos.cosmos.group.v1.DecisionPolicy
cosmos.group.v1.DecisionPolicy
cosmos/staking/v1beta1/authz.proto
(StakeAuthorization
)
Required scope:cosmos.authz.Authorization
Possible lookup scopes:
cosmos.staking.v1beta1.Authorization
cosmos.staking.Authorization
cosmos.Authorization
Authorization
Activity