fix!: update consumer chain queries #947
Annotations
10 errors and 1 warning
break-check:
proto/interchain_security/ccv/provider/v1/query.proto#L163
Field "2" with name "pagination" on message "QueryConsumerChainsRequest" changed cardinality from "optional with implicit presence" to "optional with explicit presence".
|
break-check:
proto/interchain_security/ccv/provider/v1/query.proto#L163
Field "2" with name "pagination" on message "QueryConsumerChainsRequest" changed option "json_name" from "limit" to "pagination".
|
break-check:
proto/interchain_security/ccv/provider/v1/query.proto#L163
Field "2" with name "pagination" on message "QueryConsumerChainsRequest" changed type from "int32" to "message".
|
break-check:
proto/interchain_security/ccv/provider/v1/query.proto#L163
Field "2" on message "QueryConsumerChainsRequest" changed name from "limit" to "pagination".
|
break-check:
proto/interchain_security/ccv/provider/v1/query.proto#L378
Field "1" with name "consumer_id" on message "QueryConsumerChainResponse" changed option "json_name" from "chainId" to "consumerId".
|
break-check:
proto/interchain_security/ccv/provider/v1/query.proto#L378
Field "1" on message "QueryConsumerChainResponse" changed name from "chain_id" to "consumer_id".
|
break-check:
proto/interchain_security/ccv/provider/v1/query.proto#L379
Field "2" with name "chain_id" on message "QueryConsumerChainResponse" changed option "json_name" from "ownerAddress" to "chainId".
|
break-check:
proto/interchain_security/ccv/provider/v1/query.proto#L379
Field "2" on message "QueryConsumerChainResponse" changed name from "owner_address" to "chain_id".
|
break-check:
proto/interchain_security/ccv/provider/v1/query.proto#L380
Field "3" with name "owner_address" on message "QueryConsumerChainResponse" changed option "json_name" from "phase" to "ownerAddress".
|
break-check:
proto/interchain_security/ccv/provider/v1/query.proto#L380
Field "3" on message "QueryConsumerChainResponse" changed name from "phase" to "owner_address".
|
break-check
No github_token supplied, API requests will be subject to stricter rate limiting
|