Skip to content

some accepts/implements annotations don't resolve to existing scopes #14353

Closed
@pyramation

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.Authorization
cosmos.bank.Authorization
cosmos.Authorization
Authorization
cosmos.gov.v1.Content
cosmos.gov.Content
cosmos.Content
Content
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.Authorization
cosmos.staking.Authorization
cosmos.Authorization
Authorization

Activity

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

Metadata

Assignees

No one assigned

    Labels

    C: ProtoProto definition and proto release

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions