Hydrachain-explorer-requester

Latest version: v1.0.0

Safety actively analyzes 683530 Python packages for vulnerabilities to keep your Python projects secure.

Scan your dependencies

2.0.0

**Brief summary:**
- Additional URLs to the explorer have been added
- Additional query parameters to a specific URLs have been added
- Major change in how the query parameters are passed to the library
- Internal rework of the explorer api urls retrieval logic.
- There are no more _iterator functions

**Query Parameters:**
- Additional query parameters have been added to some of the requests.
The parameters are divided into two main categories:

- **Pagination:**
- limit, offset, from, to, pageSize and page
- **Block:**
- fromBlock, toBlock, fromTime and toTime

Some of the requests accept both of these two main categories and have additional query parameters.
To deal with having too many query parameters the logic of providing them to our library has been changed. Each request, which accepts even a single query parameter now accepts a class, which represents all of his possible query parameters. Each of these classes can be overwritten, which gives the ability to even change the name of the query parameter name during request. There are examples on how to do that.
This approach not only gives us the ability to change the query parameter name during request, but also to add additional ones without breaking your previous versions, when upgrading the library and reusing the parameters across other requests.

**Iterator Functions:**
In the previous versions there were a _iterator ending functions for each request that uses pagination. From now on they are not present anymore. That was decided due to their complexity and lack of customization for a specific requests. It is now up to the consumer to define how the pagination will take place.

**URLs:**

- The whole way of using the explorer urls in the library has been changed. The constructor of the ExplorerRequester now accepts a urls parameter. It is a class that defines all of the urls to the explorer.
- That doesn't directly bother you, but gives you the ability to change the URLs if you need to. For example if you have a locally hosted test server.
- There are examples present on how to do that.

**New Requests:**


get_raw_transaction
get_address_basic_transactions
get_address_contract_transactions
get_address_contract_transactions_by_contract
get_address_utxo
get_address_balance_history
get_address_qrc20_balance_history
get_address_qrc20_balance_history_by_token
call_contract
get_search_logs
get_contract_basic_transactions

0.2.0

Implemented the **/address/:address/balance/:type** endpoint. It allows a direct retrieval of the address's:
- **Total received**
- **Total sent**
- **Unconfirmed**
- **Staking**
- **Mature**

Internal changes of the logic for requesting the explorer due to tight coupling with the json routes, which doesn't affect in any way the previous versions.

0.1.1

0.1.0

Links

Releases

Has known vulnerabilities

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.