From 7173ae8d0a12fce22b71bdc3fb156d6aff940800 Mon Sep 17 00:00:00 2001 From: swelf Date: Fri, 26 Jul 2024 16:27:47 +0300 Subject: [PATCH 1/2] upodated docs about new gov gated params --- docs/neutron/modules/interchain-queries/messages.md | 2 +- docs/neutron/modules/interchain-queries/overview.md | 4 ++-- 2 files changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/neutron/modules/interchain-queries/messages.md b/docs/neutron/modules/interchain-queries/messages.md index 397f515bb..3da5a1a1f 100644 --- a/docs/neutron/modules/interchain-queries/messages.md +++ b/docs/neutron/modules/interchain-queries/messages.md @@ -34,7 +34,7 @@ message KVKey { } ``` -> **Note:** the maximum allowed number of KVKey values for a single InterchainQuery equals to 32. +> **Note:** the maximum allowed number of KVKey values for a single InterchainQuery a module's param `MaxKvQueryKeysCount`, default value is 32. Currently `query_type` can take the following values: * `kv` - query **values** from Cosmos-SDK KV-storage on remote chain which are stored under some **keys**. In this case `kv_keys` must be filled in. diff --git a/docs/neutron/modules/interchain-queries/overview.md b/docs/neutron/modules/interchain-queries/overview.md index 1ece6eb91..957ce1d02 100644 --- a/docs/neutron/modules/interchain-queries/overview.md +++ b/docs/neutron/modules/interchain-queries/overview.md @@ -69,7 +69,7 @@ You can see more info, examples and recommendations about proper transactions re [{"field": "{eventType}.{attributeKey}", "val": "{attributeValue}", "op": "gte"}, ...] ``` -Maximum allowed amount of filters is 32. Supplying more filters than allowed will return an error. +Maximum allowed amount of filters is defined by a module's param `MaxTransactionsFilters`, the default value is 32. Supplying more filters than allowed will return an error. Supported operators: * `eq` @@ -155,7 +155,7 @@ By understanding the usage of the `transactions_filter` field, developers and us 2. **Incrementally Refine**: If needed, add additional filters incrementally to refine the results, testing at each stage to ensure relevance. 3. **Avoid Redundancy**: Ensure that each filter adds value to the query and that there are no redundant or conflicting filters. 4. **Test Performance**: Consider testing the query with different numbers of filters to gauge performance and result relevance, especially if using many filters. -5. **Use the Maximum Limit Wisely**: Note that the maximum allowed amount of 32 filters is a technical constraint. +5. **Use the Maximum Limit Wisely**: Note there is a maximum allowed amount of filters defined by a module's param `MaxTransactionsFilters`. ##### How Many Filters Do You Need? From 8bb77cc26e40b9cba48e71dfd997ed979c2f4919 Mon Sep 17 00:00:00 2001 From: swelf19 <62722506+swelf19@users.noreply.github.com> Date: Fri, 30 Aug 2024 13:06:47 +0300 Subject: [PATCH 2/2] Update docs/neutron/modules/interchain-queries/messages.md Co-authored-by: sotnikov-s <34917380+sotnikov-s@users.noreply.github.com> --- docs/neutron/modules/interchain-queries/messages.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/neutron/modules/interchain-queries/messages.md b/docs/neutron/modules/interchain-queries/messages.md index 3da5a1a1f..5dc90b99f 100644 --- a/docs/neutron/modules/interchain-queries/messages.md +++ b/docs/neutron/modules/interchain-queries/messages.md @@ -34,7 +34,7 @@ message KVKey { } ``` -> **Note:** the maximum allowed number of KVKey values for a single InterchainQuery a module's param `MaxKvQueryKeysCount`, default value is 32. +> **Note:** the maximum allowed number of KVKey values for a single InterchainQuery is defined by a module's param `MaxKvQueryKeysCount`, default value is 32. Currently `query_type` can take the following values: * `kv` - query **values** from Cosmos-SDK KV-storage on remote chain which are stored under some **keys**. In this case `kv_keys` must be filled in.