feat: upgrade Cosmos SDK to v0.47 #8484
Annotations
5 errors and 9 warnings
|
|
|
x/data/server/hasher/hasher_test.go#L12
File is not `gofmt`-ed with `-s` (gofmt)
|
|
x/data/server/genesis.go#L5
File is not `gofmt`-ed with `-s` (gofmt)
|
|
x/data/server/server.go#L5
File is not `gofmt`-ed with `-s` (gofmt)
|
|
|
|
x/data/msg_attest.go#L40
receiver-naming: receiver name msg should be consistent with previous receiver name m for MsgAttest (revive)
|
|
x/data/msg_attest.go#L41
receiver-naming: receiver name msg should be consistent with previous receiver name m for MsgAttest (revive)
|
|
x/data/msg_attest.go#L42
receiver-naming: receiver name msg should be consistent with previous receiver name m for MsgAttest (revive)
|
|
x/data/msg_define_resolver.go#L33
receiver-naming: receiver name msg should be consistent with previous receiver name m for MsgDefineResolver (revive)
|
|
x/data/msg_anchor.go#L31
receiver-naming: receiver name msg should be consistent with previous receiver name m for MsgAnchor (revive)
|
|
x/data/msg_define_resolver.go#L34
receiver-naming: receiver name msg should be consistent with previous receiver name m for MsgDefineResolver (revive)
|
|
x/data/msg_anchor.go#L32
receiver-naming: receiver name msg should be consistent with previous receiver name m for MsgAnchor (revive)
|
|
x/data/msg_define_resolver.go#L35
receiver-naming: receiver name msg should be consistent with previous receiver name m for MsgDefineResolver (revive)
|
|
x/data/msg_anchor.go#L33
receiver-naming: receiver name msg should be consistent with previous receiver name m for MsgAnchor (revive)
|
This job was cancelled
Loading