juno-network 0.4.0 → 0.5.0
Sign up to get free protection for your applications and to get access to all the features.
- package/main/codegen/cosmos/client.js +11 -5
- package/main/codegen/cosmwasm/client.js +11 -5
- package/main/codegen/ibc/client.js +11 -5
- package/package.json +3 -3
- package/types/codegen/JunoSwap.client.d.ts +120 -0
- package/types/codegen/JunoSwap.types.d.ts +124 -0
- package/types/codegen/confio/proofs.d.ts +495 -0
- package/types/codegen/contracts.d.ts +12 -0
- package/types/codegen/cosmos/app/v1alpha1/config.d.ts +51 -0
- package/types/codegen/cosmos/app/v1alpha1/module.d.ts +105 -0
- package/types/codegen/cosmos/app/v1alpha1/query.d.ts +25 -0
- package/types/codegen/cosmos/app/v1alpha1/query.rpc.query.d.ts +11 -0
- package/types/codegen/cosmos/auth/v1beta1/auth.d.ts +49 -0
- package/types/codegen/cosmos/auth/v1beta1/genesis.d.ts +18 -0
- package/types/codegen/cosmos/auth/v1beta1/query.d.ts +171 -0
- package/types/codegen/cosmos/auth/v1beta1/query.lcd.d.ts +14 -0
- package/types/codegen/cosmos/auth/v1beta1/query.rpc.query.d.ts +23 -0
- package/types/codegen/cosmos/authz/v1beta1/authz.d.ts +95 -0
- package/types/codegen/cosmos/authz/v1beta1/event.d.ts +48 -0
- package/types/codegen/cosmos/authz/v1beta1/genesis.d.ts +16 -0
- package/types/codegen/cosmos/authz/v1beta1/query.d.ts +118 -0
- package/types/codegen/cosmos/authz/v1beta1/query.lcd.d.ts +11 -0
- package/types/codegen/cosmos/authz/v1beta1/query.rpc.query.d.ts +21 -0
- package/types/codegen/cosmos/authz/v1beta1/tx.amino.d.ts +54 -0
- package/types/codegen/cosmos/authz/v1beta1/tx.d.ts +118 -0
- package/types/codegen/cosmos/authz/v1beta1/tx.registry.d.ts +76 -0
- package/types/codegen/cosmos/authz/v1beta1/tx.rpc.msg.d.ts +15 -0
- package/types/codegen/cosmos/bank/v1beta1/authz.d.ts +26 -0
- package/types/codegen/cosmos/bank/v1beta1/bank.d.ts +222 -0
- package/types/codegen/cosmos/bank/v1beta1/genesis.d.ts +62 -0
- package/types/codegen/cosmos/bank/v1beta1/query.d.ts +396 -0
- package/types/codegen/cosmos/bank/v1beta1/query.lcd.d.ts +17 -0
- package/types/codegen/cosmos/bank/v1beta1/query.rpc.query.d.ts +39 -0
- package/types/codegen/cosmos/bank/v1beta1/tx.amino.d.ts +44 -0
- package/types/codegen/cosmos/bank/v1beta1/tx.d.ts +58 -0
- package/types/codegen/cosmos/bank/v1beta1/tx.registry.d.ts +36 -0
- package/types/codegen/cosmos/bank/v1beta1/tx.rpc.msg.d.ts +13 -0
- package/types/codegen/cosmos/base/abci/v1beta1/abci.d.ts +354 -0
- package/types/codegen/cosmos/base/kv/v1beta1/kv.d.ts +25 -0
- package/types/codegen/cosmos/base/query/v1beta1/pagination.d.ts +138 -0
- package/types/codegen/cosmos/base/reflection/v1beta1/reflection.d.ts +53 -0
- package/types/codegen/cosmos/base/reflection/v2alpha1/reflection.d.ts +514 -0
- package/types/codegen/cosmos/base/snapshots/v1beta1/snapshot.d.ts +118 -0
- package/types/codegen/cosmos/base/store/v1beta1/commit_info.d.ts +47 -0
- package/types/codegen/cosmos/base/store/v1beta1/listening.d.ts +24 -0
- package/types/codegen/cosmos/base/tendermint/v1beta1/query.d.ts +197 -0
- package/types/codegen/cosmos/base/tendermint/v1beta1/query.lcd.d.ts +13 -0
- package/types/codegen/cosmos/base/tendermint/v1beta1/query.rpc.svc.d.ts +21 -0
- package/types/codegen/cosmos/base/v1beta1/coin.d.ts +78 -0
- package/types/codegen/cosmos/bundle.d.ts +6233 -0
- package/types/codegen/cosmos/capability/v1beta1/capability.d.ts +45 -0
- package/types/codegen/cosmos/capability/v1beta1/genesis.d.ts +34 -0
- package/types/codegen/cosmos/client.d.ts +473 -0
- package/types/codegen/cosmos/crisis/v1beta1/genesis.d.ts +18 -0
- package/types/codegen/cosmos/crisis/v1beta1/tx.amino.d.ts +17 -0
- package/types/codegen/cosmos/crisis/v1beta1/tx.d.ts +25 -0
- package/types/codegen/cosmos/crisis/v1beta1/tx.registry.d.ts +36 -0
- package/types/codegen/cosmos/crisis/v1beta1/tx.rpc.msg.d.ts +11 -0
- package/types/codegen/cosmos/crypto/ed25519/keys.d.ts +46 -0
- package/types/codegen/cosmos/crypto/hd/v1/hd.d.ts +39 -0
- package/types/codegen/cosmos/crypto/keyring/v1/record.d.ts +95 -0
- package/types/codegen/cosmos/crypto/multisig/keys.d.ts +26 -0
- package/types/codegen/cosmos/crypto/multisig/v1beta1/multisig.d.ts +48 -0
- package/types/codegen/cosmos/crypto/secp256k1/keys.d.ts +40 -0
- package/types/codegen/cosmos/crypto/secp256r1/keys.d.ts +38 -0
- package/types/codegen/cosmos/distribution/v1beta1/distribution.d.ts +281 -0
- package/types/codegen/cosmos/distribution/v1beta1/genesis.d.ts +224 -0
- package/types/codegen/cosmos/distribution/v1beta1/query.d.ts +385 -0
- package/types/codegen/cosmos/distribution/v1beta1/query.lcd.d.ts +17 -0
- package/types/codegen/cosmos/distribution/v1beta1/query.rpc.query.d.ts +39 -0
- package/types/codegen/cosmos/distribution/v1beta1/tx.amino.d.ts +54 -0
- package/types/codegen/cosmos/distribution/v1beta1/tx.d.ts +133 -0
- package/types/codegen/cosmos/distribution/v1beta1/tx.registry.d.ts +60 -0
- package/types/codegen/cosmos/distribution/v1beta1/tx.rpc.msg.d.ts +17 -0
- package/types/codegen/cosmos/evidence/v1beta1/evidence.d.ts +19 -0
- package/types/codegen/cosmos/evidence/v1beta1/genesis.d.ts +15 -0
- package/types/codegen/cosmos/evidence/v1beta1/query.d.ts +60 -0
- package/types/codegen/cosmos/evidence/v1beta1/query.lcd.d.ts +9 -0
- package/types/codegen/cosmos/evidence/v1beta1/query.rpc.query.d.ts +13 -0
- package/types/codegen/cosmos/evidence/v1beta1/tx.amino.d.ts +19 -0
- package/types/codegen/cosmos/evidence/v1beta1/tx.d.ts +30 -0
- package/types/codegen/cosmos/evidence/v1beta1/tx.registry.d.ts +36 -0
- package/types/codegen/cosmos/evidence/v1beta1/tx.rpc.msg.d.ts +11 -0
- package/types/codegen/cosmos/feegrant/v1beta1/feegrant.d.ts +89 -0
- package/types/codegen/cosmos/feegrant/v1beta1/genesis.d.ts +14 -0
- package/types/codegen/cosmos/feegrant/v1beta1/query.d.ts +84 -0
- package/types/codegen/cosmos/feegrant/v1beta1/query.lcd.d.ts +10 -0
- package/types/codegen/cosmos/feegrant/v1beta1/query.rpc.query.d.ts +15 -0
- package/types/codegen/cosmos/feegrant/v1beta1/tx.amino.d.ts +32 -0
- package/types/codegen/cosmos/feegrant/v1beta1/tx.d.ts +56 -0
- package/types/codegen/cosmos/feegrant/v1beta1/tx.registry.d.ts +56 -0
- package/types/codegen/cosmos/feegrant/v1beta1/tx.rpc.msg.d.ts +13 -0
- package/types/codegen/cosmos/genutil/v1beta1/genesis.d.ts +14 -0
- package/types/codegen/cosmos/gov/v1/genesis.d.ts +42 -0
- package/types/codegen/cosmos/gov/v1/gov.d.ts +301 -0
- package/types/codegen/cosmos/gov/v1/query.d.ts +298 -0
- package/types/codegen/cosmos/gov/v1/query.lcd.d.ts +16 -0
- package/types/codegen/cosmos/gov/v1/query.rpc.query.d.ts +36 -0
- package/types/codegen/cosmos/gov/v1/tx.amino.d.ts +86 -0
- package/types/codegen/cosmos/gov/v1/tx.d.ts +169 -0
- package/types/codegen/cosmos/gov/v1/tx.registry.d.ts +72 -0
- package/types/codegen/cosmos/gov/v1/tx.rpc.msg.d.ts +19 -0
- package/types/codegen/cosmos/gov/v1beta1/genesis.d.ts +42 -0
- package/types/codegen/cosmos/gov/v1beta1/gov.d.ts +338 -0
- package/types/codegen/cosmos/gov/v1beta1/query.d.ts +298 -0
- package/types/codegen/cosmos/gov/v1beta1/query.lcd.d.ts +16 -0
- package/types/codegen/cosmos/gov/v1beta1/query.rpc.query.d.ts +36 -0
- package/types/codegen/cosmos/gov/v1beta1/tx.amino.d.ts +68 -0
- package/types/codegen/cosmos/gov/v1beta1/tx.d.ts +141 -0
- package/types/codegen/cosmos/gov/v1beta1/tx.registry.d.ts +60 -0
- package/types/codegen/cosmos/gov/v1beta1/tx.rpc.msg.d.ts +17 -0
- package/types/codegen/cosmos/group/v1/events.d.ts +115 -0
- package/types/codegen/cosmos/group/v1/genesis.d.ts +38 -0
- package/types/codegen/cosmos/group/v1/query.d.ts +350 -0
- package/types/codegen/cosmos/group/v1/query.lcd.d.ts +20 -0
- package/types/codegen/cosmos/group/v1/query.rpc.query.d.ts +35 -0
- package/types/codegen/cosmos/group/v1/tx.amino.d.ts +227 -0
- package/types/codegen/cosmos/group/v1/tx.d.ts +419 -0
- package/types/codegen/cosmos/group/v1/tx.registry.d.ts +296 -0
- package/types/codegen/cosmos/group/v1/tx.rpc.msg.d.ts +37 -0
- package/types/codegen/cosmos/group/v1/types.d.ts +324 -0
- package/types/codegen/cosmos/lcd.d.ts +28 -0
- package/types/codegen/cosmos/mint/v1beta1/genesis.d.ts +17 -0
- package/types/codegen/cosmos/mint/v1beta1/mint.d.ts +38 -0
- package/types/codegen/cosmos/mint/v1beta1/query.d.ts +78 -0
- package/types/codegen/cosmos/mint/v1beta1/query.lcd.d.ts +10 -0
- package/types/codegen/cosmos/mint/v1beta1/query.rpc.query.d.ts +15 -0
- package/types/codegen/cosmos/msg/v1/msg.d.ts +1 -0
- package/types/codegen/cosmos/nft/v1beta1/event.d.ts +42 -0
- package/types/codegen/cosmos/nft/v1beta1/genesis.d.ts +30 -0
- package/types/codegen/cosmos/nft/v1beta1/nft.d.ts +47 -0
- package/types/codegen/cosmos/nft/v1beta1/query.d.ts +166 -0
- package/types/codegen/cosmos/nft/v1beta1/query.lcd.d.ts +14 -0
- package/types/codegen/cosmos/nft/v1beta1/query.rpc.query.d.ts +23 -0
- package/types/codegen/cosmos/nft/v1beta1/tx.amino.d.ts +18 -0
- package/types/codegen/cosmos/nft/v1beta1/tx.d.ts +30 -0
- package/types/codegen/cosmos/nft/v1beta1/tx.registry.d.ts +36 -0
- package/types/codegen/cosmos/nft/v1beta1/tx.rpc.msg.d.ts +11 -0
- package/types/codegen/cosmos/orm/v1/orm.d.ts +117 -0
- package/types/codegen/cosmos/orm/v1alpha1/schema.d.ts +90 -0
- package/types/codegen/cosmos/params/v1beta1/params.d.ts +31 -0
- package/types/codegen/cosmos/params/v1beta1/query.d.ts +71 -0
- package/types/codegen/cosmos/params/v1beta1/query.lcd.d.ts +9 -0
- package/types/codegen/cosmos/params/v1beta1/query.rpc.query.d.ts +13 -0
- package/types/codegen/cosmos/rpc.query.d.ts +97 -0
- package/types/codegen/cosmos/rpc.tx.d.ts +26 -0
- package/types/codegen/cosmos/slashing/v1beta1/genesis.d.ts +70 -0
- package/types/codegen/cosmos/slashing/v1beta1/query.d.ts +85 -0
- package/types/codegen/cosmos/slashing/v1beta1/query.lcd.d.ts +10 -0
- package/types/codegen/cosmos/slashing/v1beta1/query.rpc.query.d.ts +15 -0
- package/types/codegen/cosmos/slashing/v1beta1/slashing.d.ts +52 -0
- package/types/codegen/cosmos/slashing/v1beta1/tx.amino.d.ts +15 -0
- package/types/codegen/cosmos/slashing/v1beta1/tx.d.ts +23 -0
- package/types/codegen/cosmos/slashing/v1beta1/tx.registry.d.ts +36 -0
- package/types/codegen/cosmos/slashing/v1beta1/tx.rpc.msg.d.ts +11 -0
- package/types/codegen/cosmos/staking/v1beta1/authz.d.ts +97 -0
- package/types/codegen/cosmos/staking/v1beta1/genesis.d.ts +75 -0
- package/types/codegen/cosmos/staking/v1beta1/query.d.ts +592 -0
- package/types/codegen/cosmos/staking/v1beta1/query.lcd.d.ts +22 -0
- package/types/codegen/cosmos/staking/v1beta1/query.rpc.query.d.ts +54 -0
- package/types/codegen/cosmos/staking/v1beta1/staking.d.ts +568 -0
- package/types/codegen/cosmos/staking/v1beta1/tx.amino.d.ts +106 -0
- package/types/codegen/cosmos/staking/v1beta1/tx.d.ts +191 -0
- package/types/codegen/cosmos/staking/v1beta1/tx.registry.d.ts +72 -0
- package/types/codegen/cosmos/staking/v1beta1/tx.rpc.msg.d.ts +19 -0
- package/types/codegen/cosmos/tx/signing/v1beta1/signing.d.ts +203 -0
- package/types/codegen/cosmos/tx/v1beta1/service.d.ts +339 -0
- package/types/codegen/cosmos/tx/v1beta1/service.lcd.d.ts +11 -0
- package/types/codegen/cosmos/tx/v1beta1/service.rpc.svc.d.ts +27 -0
- package/types/codegen/cosmos/tx/v1beta1/tx.d.ts +603 -0
- package/types/codegen/cosmos/upgrade/v1beta1/query.d.ts +233 -0
- package/types/codegen/cosmos/upgrade/v1beta1/query.lcd.d.ts +13 -0
- package/types/codegen/cosmos/upgrade/v1beta1/query.rpc.query.d.ts +27 -0
- package/types/codegen/cosmos/upgrade/v1beta1/tx.amino.d.ts +39 -0
- package/types/codegen/cosmos/upgrade/v1beta1/tx.d.ts +91 -0
- package/types/codegen/cosmos/upgrade/v1beta1/tx.registry.d.ts +36 -0
- package/types/codegen/cosmos/upgrade/v1beta1/tx.rpc.msg.d.ts +13 -0
- package/types/codegen/cosmos/upgrade/v1beta1/upgrade.d.ts +165 -0
- package/types/codegen/cosmos/vesting/v1beta1/tx.amino.d.ts +58 -0
- package/types/codegen/cosmos/vesting/v1beta1/tx.d.ts +88 -0
- package/types/codegen/cosmos/vesting/v1beta1/tx.registry.d.ts +76 -0
- package/types/codegen/cosmos/vesting/v1beta1/tx.rpc.msg.d.ts +15 -0
- package/types/codegen/cosmos/vesting/v1beta1/vesting.d.ts +97 -0
- package/types/codegen/cosmos_proto/bundle.d.ts +24 -0
- package/types/codegen/cosmos_proto/cosmos.d.ts +124 -0
- package/types/codegen/cosmwasm/bundle.d.ts +1109 -0
- package/types/codegen/cosmwasm/client.d.ts +120 -0
- package/types/codegen/cosmwasm/lcd.d.ts +33 -0
- package/types/codegen/cosmwasm/rpc.query.d.ts +112 -0
- package/types/codegen/cosmwasm/rpc.tx.d.ts +31 -0
- package/types/codegen/cosmwasm/wasm/v1/genesis.d.ts +101 -0
- package/types/codegen/cosmwasm/wasm/v1/ibc.d.ts +60 -0
- package/types/codegen/cosmwasm/wasm/v1/proposal.d.ts +297 -0
- package/types/codegen/cosmwasm/wasm/v1/query.d.ts +411 -0
- package/types/codegen/cosmwasm/wasm/v1/query.lcd.d.ts +17 -0
- package/types/codegen/cosmwasm/wasm/v1/query.rpc.query.d.ts +39 -0
- package/types/codegen/cosmwasm/wasm/v1/tx.amino.d.ts +95 -0
- package/types/codegen/cosmwasm/wasm/v1/tx.d.ts +262 -0
- package/types/codegen/cosmwasm/wasm/v1/tx.registry.d.ts +84 -0
- package/types/codegen/cosmwasm/wasm/v1/tx.rpc.msg.d.ts +21 -0
- package/types/codegen/cosmwasm/wasm/v1/types.d.ts +247 -0
- package/types/codegen/gogoproto/bundle.d.ts +1 -0
- package/types/codegen/gogoproto/gogo.d.ts +1 -0
- package/types/codegen/google/api/annotations.d.ts +1 -0
- package/types/codegen/google/api/http.d.ts +375 -0
- package/types/codegen/google/bundle.d.ts +1545 -0
- package/types/codegen/google/protobuf/any.d.ts +237 -0
- package/types/codegen/google/protobuf/descriptor.d.ts +1725 -0
- package/types/codegen/google/protobuf/duration.d.ts +161 -0
- package/types/codegen/google/protobuf/empty.d.ts +33 -0
- package/types/codegen/google/protobuf/field_mask.d.ts +417 -0
- package/types/codegen/google/protobuf/struct.d.ts +148 -0
- package/types/codegen/google/protobuf/timestamp.d.ts +205 -0
- package/types/codegen/google/protobuf/wrappers.d.ts +209 -0
- package/types/codegen/ibc/applications/transfer/v1/genesis.d.ts +20 -0
- package/types/codegen/ibc/applications/transfer/v1/query.d.ts +118 -0
- package/types/codegen/ibc/applications/transfer/v1/query.lcd.d.ts +11 -0
- package/types/codegen/ibc/applications/transfer/v1/query.rpc.query.d.ts +21 -0
- package/types/codegen/ibc/applications/transfer/v1/transfer.d.ts +74 -0
- package/types/codegen/ibc/applications/transfer/v1/tx.amino.d.ts +25 -0
- package/types/codegen/ibc/applications/transfer/v1/tx.d.ts +74 -0
- package/types/codegen/ibc/applications/transfer/v1/tx.registry.d.ts +24 -0
- package/types/codegen/ibc/applications/transfer/v1/tx.rpc.msg.d.ts +11 -0
- package/types/codegen/ibc/applications/transfer/v2/packet.d.ts +37 -0
- package/types/codegen/ibc/bundle.d.ts +3781 -0
- package/types/codegen/ibc/client.d.ts +559 -0
- package/types/codegen/ibc/core/channel/v1/channel.d.ts +313 -0
- package/types/codegen/ibc/core/channel/v1/genesis.d.ts +55 -0
- package/types/codegen/ibc/core/channel/v1/query.d.ts +726 -0
- package/types/codegen/ibc/core/channel/v1/query.lcd.d.ts +21 -0
- package/types/codegen/ibc/core/channel/v1/query.rpc.query.d.ts +51 -0
- package/types/codegen/ibc/core/channel/v1/tx.amino.d.ts +209 -0
- package/types/codegen/ibc/core/channel/v1/tx.d.ts +380 -0
- package/types/codegen/ibc/core/channel/v1/tx.registry.d.ts +132 -0
- package/types/codegen/ibc/core/channel/v1/tx.rpc.msg.d.ts +29 -0
- package/types/codegen/ibc/core/client/v1/client.d.ts +219 -0
- package/types/codegen/ibc/core/client/v1/genesis.d.ts +82 -0
- package/types/codegen/ibc/core/client/v1/query.d.ts +377 -0
- package/types/codegen/ibc/core/client/v1/query.lcd.d.ts +16 -0
- package/types/codegen/ibc/core/client/v1/query.rpc.query.d.ts +36 -0
- package/types/codegen/ibc/core/client/v1/tx.amino.d.ts +77 -0
- package/types/codegen/ibc/core/client/v1/tx.d.ts +187 -0
- package/types/codegen/ibc/core/client/v1/tx.registry.d.ts +60 -0
- package/types/codegen/ibc/core/client/v1/tx.rpc.msg.d.ts +17 -0
- package/types/codegen/ibc/core/commitment/v1/commitment.d.ts +89 -0
- package/types/codegen/ibc/core/connection/v1/connection.d.ts +260 -0
- package/types/codegen/ibc/core/connection/v1/genesis.d.ts +24 -0
- package/types/codegen/ibc/core/connection/v1/query.d.ts +264 -0
- package/types/codegen/ibc/core/connection/v1/query.lcd.d.ts +13 -0
- package/types/codegen/ibc/core/connection/v1/query.rpc.query.d.ts +27 -0
- package/types/codegen/ibc/core/connection/v1/tx.amino.d.ts +103 -0
- package/types/codegen/ibc/core/connection/v1/tx.d.ts +225 -0
- package/types/codegen/ibc/core/connection/v1/tx.registry.d.ts +60 -0
- package/types/codegen/ibc/core/connection/v1/tx.rpc.msg.d.ts +17 -0
- package/types/codegen/ibc/core/port/v1/query.d.ts +37 -0
- package/types/codegen/ibc/core/port/v1/query.rpc.query.d.ts +11 -0
- package/types/codegen/ibc/core/types/v1/genesis.d.ts +21 -0
- package/types/codegen/ibc/lcd.d.ts +46 -0
- package/types/codegen/ibc/lightclients/localhost/v1/localhost.d.ts +28 -0
- package/types/codegen/ibc/lightclients/solomachine/v1/solomachine.d.ts +433 -0
- package/types/codegen/ibc/lightclients/solomachine/v2/solomachine.d.ts +433 -0
- package/types/codegen/ibc/lightclients/tendermint/v1/tendermint.d.ts +215 -0
- package/types/codegen/ibc/rpc.query.d.ts +148 -0
- package/types/codegen/ibc/rpc.tx.d.ts +44 -0
- package/types/codegen/ics23/bundle.d.ts +545 -0
- package/types/codegen/index.d.ts +18 -0
- package/types/codegen/juno/bundle.d.ts +226 -0
- package/types/codegen/juno/lcd.d.ts +31 -0
- package/types/codegen/juno/mint/genesis.d.ts +22 -0
- package/types/codegen/juno/mint/mint.d.ts +44 -0
- package/types/codegen/juno/mint/query.d.ts +99 -0
- package/types/codegen/juno/mint/query.lcd.d.ts +11 -0
- package/types/codegen/juno/mint/query.rpc.query.d.ts +21 -0
- package/types/codegen/juno/rpc.query.d.ts +104 -0
- package/types/codegen/tendermint/abci/types.d.ts +902 -0
- package/types/codegen/tendermint/bundle.d.ts +2065 -0
- package/types/codegen/tendermint/crypto/keys.d.ts +17 -0
- package/types/codegen/tendermint/crypto/proof.d.ts +89 -0
- package/types/codegen/tendermint/libs/bits/types.d.ts +15 -0
- package/types/codegen/tendermint/p2p/types.d.ts +87 -0
- package/types/codegen/tendermint/types/block.d.ts +21 -0
- package/types/codegen/tendermint/types/evidence.d.ts +70 -0
- package/types/codegen/tendermint/types/params.d.ts +181 -0
- package/types/codegen/tendermint/types/types.d.ts +326 -0
- package/types/codegen/tendermint/types/validator.d.ts +48 -0
- package/types/codegen/tendermint/version/types.d.ts +48 -0
- package/types/index.d.ts +1 -0
@@ -0,0 +1,375 @@
|
|
1
|
+
import * as _m0 from "protobufjs/minimal";
|
2
|
+
import { DeepPartial } from "@osmonauts/helpers";
|
3
|
+
/**
|
4
|
+
* Defines the HTTP configuration for an API service. It contains a list of
|
5
|
+
* [HttpRule][google.api.HttpRule], each specifying the mapping of an RPC method
|
6
|
+
* to one or more HTTP REST API methods.
|
7
|
+
*/
|
8
|
+
export interface Http {
|
9
|
+
/**
|
10
|
+
* A list of HTTP configuration rules that apply to individual API methods.
|
11
|
+
*
|
12
|
+
* **NOTE:** All service configuration rules follow "last one wins" order.
|
13
|
+
*/
|
14
|
+
rules: HttpRule[];
|
15
|
+
/**
|
16
|
+
* When set to true, URL path parameters will be fully URI-decoded except in
|
17
|
+
* cases of single segment matches in reserved expansion, where "%2F" will be
|
18
|
+
* left encoded.
|
19
|
+
*
|
20
|
+
* The default behavior is to not decode RFC 6570 reserved characters in multi
|
21
|
+
* segment matches.
|
22
|
+
*/
|
23
|
+
fully_decode_reserved_expansion: boolean;
|
24
|
+
}
|
25
|
+
/**
|
26
|
+
* # gRPC Transcoding
|
27
|
+
*
|
28
|
+
* gRPC Transcoding is a feature for mapping between a gRPC method and one or
|
29
|
+
* more HTTP REST endpoints. It allows developers to build a single API service
|
30
|
+
* that supports both gRPC APIs and REST APIs. Many systems, including [Google
|
31
|
+
* APIs](https://github.com/googleapis/googleapis),
|
32
|
+
* [Cloud Endpoints](https://cloud.google.com/endpoints), [gRPC
|
33
|
+
* Gateway](https://github.com/grpc-ecosystem/grpc-gateway),
|
34
|
+
* and [Envoy](https://github.com/envoyproxy/envoy) proxy support this feature
|
35
|
+
* and use it for large scale production services.
|
36
|
+
*
|
37
|
+
* `HttpRule` defines the schema of the gRPC/REST mapping. The mapping specifies
|
38
|
+
* how different portions of the gRPC request message are mapped to the URL
|
39
|
+
* path, URL query parameters, and HTTP request body. It also controls how the
|
40
|
+
* gRPC response message is mapped to the HTTP response body. `HttpRule` is
|
41
|
+
* typically specified as an `google.api.http` annotation on the gRPC method.
|
42
|
+
*
|
43
|
+
* Each mapping specifies a URL path template and an HTTP method. The path
|
44
|
+
* template may refer to one or more fields in the gRPC request message, as long
|
45
|
+
* as each field is a non-repeated field with a primitive (non-message) type.
|
46
|
+
* The path template controls how fields of the request message are mapped to
|
47
|
+
* the URL path.
|
48
|
+
*
|
49
|
+
* Example:
|
50
|
+
*
|
51
|
+
* service Messaging {
|
52
|
+
* rpc GetMessage(GetMessageRequest) returns (Message) {
|
53
|
+
* option (google.api.http) = {
|
54
|
+
* get: "/v1/{name=messages/*}"
|
55
|
+
* };
|
56
|
+
* }
|
57
|
+
* }
|
58
|
+
* message GetMessageRequest {
|
59
|
+
* string name = 1; // Mapped to URL path.
|
60
|
+
* }
|
61
|
+
* message Message {
|
62
|
+
* string text = 1; // The resource content.
|
63
|
+
* }
|
64
|
+
*
|
65
|
+
* This enables an HTTP REST to gRPC mapping as below:
|
66
|
+
*
|
67
|
+
* HTTP | gRPC
|
68
|
+
* -----|-----
|
69
|
+
* `GET /v1/messages/123456` | `GetMessage(name: "messages/123456")`
|
70
|
+
*
|
71
|
+
* Any fields in the request message which are not bound by the path template
|
72
|
+
* automatically become HTTP query parameters if there is no HTTP request body.
|
73
|
+
* For example:
|
74
|
+
*
|
75
|
+
* service Messaging {
|
76
|
+
* rpc GetMessage(GetMessageRequest) returns (Message) {
|
77
|
+
* option (google.api.http) = {
|
78
|
+
* get:"/v1/messages/{message_id}"
|
79
|
+
* };
|
80
|
+
* }
|
81
|
+
* }
|
82
|
+
* message GetMessageRequest {
|
83
|
+
* message SubMessage {
|
84
|
+
* string subfield = 1;
|
85
|
+
* }
|
86
|
+
* string message_id = 1; // Mapped to URL path.
|
87
|
+
* int64 revision = 2; // Mapped to URL query parameter `revision`.
|
88
|
+
* SubMessage sub = 3; // Mapped to URL query parameter `sub.subfield`.
|
89
|
+
* }
|
90
|
+
*
|
91
|
+
* This enables a HTTP JSON to RPC mapping as below:
|
92
|
+
*
|
93
|
+
* HTTP | gRPC
|
94
|
+
* -----|-----
|
95
|
+
* `GET /v1/messages/123456?revision=2&sub.subfield=foo` |
|
96
|
+
* `GetMessage(message_id: "123456" revision: 2 sub: SubMessage(subfield:
|
97
|
+
* "foo"))`
|
98
|
+
*
|
99
|
+
* Note that fields which are mapped to URL query parameters must have a
|
100
|
+
* primitive type or a repeated primitive type or a non-repeated message type.
|
101
|
+
* In the case of a repeated type, the parameter can be repeated in the URL
|
102
|
+
* as `...?param=A¶m=B`. In the case of a message type, each field of the
|
103
|
+
* message is mapped to a separate parameter, such as
|
104
|
+
* `...?foo.a=A&foo.b=B&foo.c=C`.
|
105
|
+
*
|
106
|
+
* For HTTP methods that allow a request body, the `body` field
|
107
|
+
* specifies the mapping. Consider a REST update method on the
|
108
|
+
* message resource collection:
|
109
|
+
*
|
110
|
+
* service Messaging {
|
111
|
+
* rpc UpdateMessage(UpdateMessageRequest) returns (Message) {
|
112
|
+
* option (google.api.http) = {
|
113
|
+
* patch: "/v1/messages/{message_id}"
|
114
|
+
* body: "message"
|
115
|
+
* };
|
116
|
+
* }
|
117
|
+
* }
|
118
|
+
* message UpdateMessageRequest {
|
119
|
+
* string message_id = 1; // mapped to the URL
|
120
|
+
* Message message = 2; // mapped to the body
|
121
|
+
* }
|
122
|
+
*
|
123
|
+
* The following HTTP JSON to RPC mapping is enabled, where the
|
124
|
+
* representation of the JSON in the request body is determined by
|
125
|
+
* protos JSON encoding:
|
126
|
+
*
|
127
|
+
* HTTP | gRPC
|
128
|
+
* -----|-----
|
129
|
+
* `PATCH /v1/messages/123456 { "text": "Hi!" }` | `UpdateMessage(message_id:
|
130
|
+
* "123456" message { text: "Hi!" })`
|
131
|
+
*
|
132
|
+
* The special name `*` can be used in the body mapping to define that
|
133
|
+
* every field not bound by the path template should be mapped to the
|
134
|
+
* request body. This enables the following alternative definition of
|
135
|
+
* the update method:
|
136
|
+
*
|
137
|
+
* service Messaging {
|
138
|
+
* rpc UpdateMessage(Message) returns (Message) {
|
139
|
+
* option (google.api.http) = {
|
140
|
+
* patch: "/v1/messages/{message_id}"
|
141
|
+
* body: "*"
|
142
|
+
* };
|
143
|
+
* }
|
144
|
+
* }
|
145
|
+
* message Message {
|
146
|
+
* string message_id = 1;
|
147
|
+
* string text = 2;
|
148
|
+
* }
|
149
|
+
*
|
150
|
+
*
|
151
|
+
* The following HTTP JSON to RPC mapping is enabled:
|
152
|
+
*
|
153
|
+
* HTTP | gRPC
|
154
|
+
* -----|-----
|
155
|
+
* `PATCH /v1/messages/123456 { "text": "Hi!" }` | `UpdateMessage(message_id:
|
156
|
+
* "123456" text: "Hi!")`
|
157
|
+
*
|
158
|
+
* Note that when using `*` in the body mapping, it is not possible to
|
159
|
+
* have HTTP parameters, as all fields not bound by the path end in
|
160
|
+
* the body. This makes this option more rarely used in practice when
|
161
|
+
* defining REST APIs. The common usage of `*` is in custom methods
|
162
|
+
* which don't use the URL at all for transferring data.
|
163
|
+
*
|
164
|
+
* It is possible to define multiple HTTP methods for one RPC by using
|
165
|
+
* the `additional_bindings` option. Example:
|
166
|
+
*
|
167
|
+
* service Messaging {
|
168
|
+
* rpc GetMessage(GetMessageRequest) returns (Message) {
|
169
|
+
* option (google.api.http) = {
|
170
|
+
* get: "/v1/messages/{message_id}"
|
171
|
+
* additional_bindings {
|
172
|
+
* get: "/v1/users/{user_id}/messages/{message_id}"
|
173
|
+
* }
|
174
|
+
* };
|
175
|
+
* }
|
176
|
+
* }
|
177
|
+
* message GetMessageRequest {
|
178
|
+
* string message_id = 1;
|
179
|
+
* string user_id = 2;
|
180
|
+
* }
|
181
|
+
*
|
182
|
+
* This enables the following two alternative HTTP JSON to RPC mappings:
|
183
|
+
*
|
184
|
+
* HTTP | gRPC
|
185
|
+
* -----|-----
|
186
|
+
* `GET /v1/messages/123456` | `GetMessage(message_id: "123456")`
|
187
|
+
* `GET /v1/users/me/messages/123456` | `GetMessage(user_id: "me" message_id:
|
188
|
+
* "123456")`
|
189
|
+
*
|
190
|
+
* ## Rules for HTTP mapping
|
191
|
+
*
|
192
|
+
* 1. Leaf request fields (recursive expansion nested messages in the request
|
193
|
+
* message) are classified into three categories:
|
194
|
+
* - Fields referred by the path template. They are passed via the URL path.
|
195
|
+
* - Fields referred by the [HttpRule.body][google.api.HttpRule.body]. They are passed via the HTTP
|
196
|
+
* request body.
|
197
|
+
* - All other fields are passed via the URL query parameters, and the
|
198
|
+
* parameter name is the field path in the request message. A repeated
|
199
|
+
* field can be represented as multiple query parameters under the same
|
200
|
+
* name.
|
201
|
+
* 2. If [HttpRule.body][google.api.HttpRule.body] is "*", there is no URL query parameter, all fields
|
202
|
+
* are passed via URL path and HTTP request body.
|
203
|
+
* 3. If [HttpRule.body][google.api.HttpRule.body] is omitted, there is no HTTP request body, all
|
204
|
+
* fields are passed via URL path and URL query parameters.
|
205
|
+
*
|
206
|
+
* ### Path template syntax
|
207
|
+
*
|
208
|
+
* Template = "/" Segments [ Verb ] ;
|
209
|
+
* Segments = Segment { "/" Segment } ;
|
210
|
+
* Segment = "*" | "**" | LITERAL | Variable ;
|
211
|
+
* Variable = "{" FieldPath [ "=" Segments ] "}" ;
|
212
|
+
* FieldPath = IDENT { "." IDENT } ;
|
213
|
+
* Verb = ":" LITERAL ;
|
214
|
+
*
|
215
|
+
* The syntax `*` matches a single URL path segment. The syntax `**` matches
|
216
|
+
* zero or more URL path segments, which must be the last part of the URL path
|
217
|
+
* except the `Verb`.
|
218
|
+
*
|
219
|
+
* The syntax `Variable` matches part of the URL path as specified by its
|
220
|
+
* template. A variable template must not contain other variables. If a variable
|
221
|
+
* matches a single path segment, its template may be omitted, e.g. `{var}`
|
222
|
+
* is equivalent to `{var=*}`.
|
223
|
+
*
|
224
|
+
* The syntax `LITERAL` matches literal text in the URL path. If the `LITERAL`
|
225
|
+
* contains any reserved character, such characters should be percent-encoded
|
226
|
+
* before the matching.
|
227
|
+
*
|
228
|
+
* If a variable contains exactly one path segment, such as `"{var}"` or
|
229
|
+
* `"{var=*}"`, when such a variable is expanded into a URL path on the client
|
230
|
+
* side, all characters except `[-_.~0-9a-zA-Z]` are percent-encoded. The
|
231
|
+
* server side does the reverse decoding. Such variables show up in the
|
232
|
+
* [Discovery
|
233
|
+
* Document](https://developers.google.com/discovery/v1/reference/apis) as
|
234
|
+
* `{var}`.
|
235
|
+
*
|
236
|
+
* If a variable contains multiple path segments, such as `"{var=foo/*}"`
|
237
|
+
* or `"{var=**}"`, when such a variable is expanded into a URL path on the
|
238
|
+
* client side, all characters except `[-_.~/0-9a-zA-Z]` are percent-encoded.
|
239
|
+
* The server side does the reverse decoding, except "%2F" and "%2f" are left
|
240
|
+
* unchanged. Such variables show up in the
|
241
|
+
* [Discovery
|
242
|
+
* Document](https://developers.google.com/discovery/v1/reference/apis) as
|
243
|
+
* `{+var}`.
|
244
|
+
*
|
245
|
+
* ## Using gRPC API Service Configuration
|
246
|
+
*
|
247
|
+
* gRPC API Service Configuration (service config) is a configuration language
|
248
|
+
* for configuring a gRPC service to become a user-facing product. The
|
249
|
+
* service config is simply the YAML representation of the `google.api.Service`
|
250
|
+
* proto message.
|
251
|
+
*
|
252
|
+
* As an alternative to annotating your proto file, you can configure gRPC
|
253
|
+
* transcoding in your service config YAML files. You do this by specifying a
|
254
|
+
* `HttpRule` that maps the gRPC method to a REST endpoint, achieving the same
|
255
|
+
* effect as the proto annotation. This can be particularly useful if you
|
256
|
+
* have a proto that is reused in multiple services. Note that any transcoding
|
257
|
+
* specified in the service config will override any matching transcoding
|
258
|
+
* configuration in the proto.
|
259
|
+
*
|
260
|
+
* Example:
|
261
|
+
*
|
262
|
+
* http:
|
263
|
+
* rules:
|
264
|
+
* # Selects a gRPC method and applies HttpRule to it.
|
265
|
+
* - selector: example.v1.Messaging.GetMessage
|
266
|
+
* get: /v1/messages/{message_id}/{sub.subfield}
|
267
|
+
*
|
268
|
+
* ## Special notes
|
269
|
+
*
|
270
|
+
* When gRPC Transcoding is used to map a gRPC to JSON REST endpoints, the
|
271
|
+
* proto to JSON conversion must follow the [proto3
|
272
|
+
* specification](https://developers.google.com/protocol-buffers/docs/proto3#json).
|
273
|
+
*
|
274
|
+
* While the single segment variable follows the semantics of
|
275
|
+
* [RFC 6570](https://tools.ietf.org/html/rfc6570) Section 3.2.2 Simple String
|
276
|
+
* Expansion, the multi segment variable **does not** follow RFC 6570 Section
|
277
|
+
* 3.2.3 Reserved Expansion. The reason is that the Reserved Expansion
|
278
|
+
* does not expand special characters like `?` and `#`, which would lead
|
279
|
+
* to invalid URLs. As the result, gRPC Transcoding uses a custom encoding
|
280
|
+
* for multi segment variables.
|
281
|
+
*
|
282
|
+
* The path variables **must not** refer to any repeated or mapped field,
|
283
|
+
* because client libraries are not capable of handling such variable expansion.
|
284
|
+
*
|
285
|
+
* The path variables **must not** capture the leading "/" character. The reason
|
286
|
+
* is that the most common use case "{var}" does not capture the leading "/"
|
287
|
+
* character. For consistency, all path variables must share the same behavior.
|
288
|
+
*
|
289
|
+
* Repeated message fields must not be mapped to URL query parameters, because
|
290
|
+
* no client library can support such complicated mapping.
|
291
|
+
*
|
292
|
+
* If an API needs to use a JSON array for request or response body, it can map
|
293
|
+
* the request or response body to a repeated field. However, some gRPC
|
294
|
+
* Transcoding implementations may not support this feature.
|
295
|
+
*/
|
296
|
+
export interface HttpRule {
|
297
|
+
/**
|
298
|
+
* Selects a method to which this rule applies.
|
299
|
+
*
|
300
|
+
* Refer to [selector][google.api.DocumentationRule.selector] for syntax details.
|
301
|
+
*/
|
302
|
+
selector: string;
|
303
|
+
/**
|
304
|
+
* Maps to HTTP GET. Used for listing and getting information about
|
305
|
+
* resources.
|
306
|
+
*/
|
307
|
+
get?: string;
|
308
|
+
/** Maps to HTTP PUT. Used for replacing a resource. */
|
309
|
+
put?: string;
|
310
|
+
/** Maps to HTTP POST. Used for creating a resource or performing an action. */
|
311
|
+
post?: string;
|
312
|
+
/** Maps to HTTP DELETE. Used for deleting a resource. */
|
313
|
+
delete?: string;
|
314
|
+
/** Maps to HTTP PATCH. Used for updating a resource. */
|
315
|
+
patch?: string;
|
316
|
+
/**
|
317
|
+
* The custom pattern is used for specifying an HTTP method that is not
|
318
|
+
* included in the `pattern` field, such as HEAD, or "*" to leave the
|
319
|
+
* HTTP method unspecified for this rule. The wild-card rule is useful
|
320
|
+
* for services that provide content to Web (HTML) clients.
|
321
|
+
*/
|
322
|
+
custom?: CustomHttpPattern;
|
323
|
+
/**
|
324
|
+
* The name of the request field whose value is mapped to the HTTP request
|
325
|
+
* body, or `*` for mapping all request fields not captured by the path
|
326
|
+
* pattern to the HTTP body, or omitted for not having any HTTP request body.
|
327
|
+
*
|
328
|
+
* NOTE: the referred field must be present at the top-level of the request
|
329
|
+
* message type.
|
330
|
+
*/
|
331
|
+
body: string;
|
332
|
+
/**
|
333
|
+
* Optional. The name of the response field whose value is mapped to the HTTP
|
334
|
+
* response body. When omitted, the entire response message will be used
|
335
|
+
* as the HTTP response body.
|
336
|
+
*
|
337
|
+
* NOTE: The referred field must be present at the top-level of the response
|
338
|
+
* message type.
|
339
|
+
*/
|
340
|
+
response_body: string;
|
341
|
+
/**
|
342
|
+
* Additional HTTP bindings for the selector. Nested bindings must
|
343
|
+
* not contain an `additional_bindings` field themselves (that is,
|
344
|
+
* the nesting may only be one level deep).
|
345
|
+
*/
|
346
|
+
additional_bindings: HttpRule[];
|
347
|
+
}
|
348
|
+
/** A custom pattern is used for defining custom HTTP verb. */
|
349
|
+
export interface CustomHttpPattern {
|
350
|
+
/** The name of this custom HTTP verb. */
|
351
|
+
kind: string;
|
352
|
+
/** The path matched by this custom verb. */
|
353
|
+
path: string;
|
354
|
+
}
|
355
|
+
export declare const Http: {
|
356
|
+
encode(message: Http, writer?: _m0.Writer): _m0.Writer;
|
357
|
+
decode(input: _m0.Reader | Uint8Array, length?: number): Http;
|
358
|
+
fromJSON(object: any): Http;
|
359
|
+
toJSON(message: Http): unknown;
|
360
|
+
fromPartial(object: DeepPartial<Http>): Http;
|
361
|
+
};
|
362
|
+
export declare const HttpRule: {
|
363
|
+
encode(message: HttpRule, writer?: _m0.Writer): _m0.Writer;
|
364
|
+
decode(input: _m0.Reader | Uint8Array, length?: number): HttpRule;
|
365
|
+
fromJSON(object: any): HttpRule;
|
366
|
+
toJSON(message: HttpRule): unknown;
|
367
|
+
fromPartial(object: DeepPartial<HttpRule>): HttpRule;
|
368
|
+
};
|
369
|
+
export declare const CustomHttpPattern: {
|
370
|
+
encode(message: CustomHttpPattern, writer?: _m0.Writer): _m0.Writer;
|
371
|
+
decode(input: _m0.Reader | Uint8Array, length?: number): CustomHttpPattern;
|
372
|
+
fromJSON(object: any): CustomHttpPattern;
|
373
|
+
toJSON(message: CustomHttpPattern): unknown;
|
374
|
+
fromPartial(object: DeepPartial<CustomHttpPattern>): CustomHttpPattern;
|
375
|
+
};
|