PR-650 @web3api/cli: Add YAML support for query recipes.
PR-385 @web3api/cli, @web3api/client-js: Use JSON for manifest build artifacts.
PR-678 @web3api/cli: Build command no longer uses same docker image name by default. The concept of a "build UUID" has been added, and will be appended to the docker image name (if the develoer has not specified their own inside web3api.build.yaml).
PR-610 @web3api/client-js: Support the resolveUri(...) method on Web3ApiClient instances.

Bugs

PR-665 @web3api/ethereum-plugin-js: Fix TxRequest property mapping to ethers.js types.
PR-672 @web3api/core-js, @web3api/schema-bind, @web3api/schema-parse: Remove use of the JS string .substr method.
PR-673 @web3api/cli: The w3 query ... command now property sets exitCode to 1 if a query fails.
PR-651 @web3api/http-plugin-js: JSON payloads are now property supported.

Breaking Changes

PR-674 @web3api/cli, @web3api/schema-bind: Return Result<T, E> objects from all AssemblyScript subinvoke methods.

Readme

Source

Tracing

Steps to use tracing

Run the zipkin client using docker
```
docker run -d -p 9411:9411 openzipkin/zipkin
```
Enable tracing when creating the Web3ApiClient
```
const client = new Web3ApiClient({
  ...,
  tracingEnabled: true
})
```
Or you can turn on tracing while running the Web3ApiClient by calling the tracingEnabled method of Web3ApiClient.
```
// Turn tracing off
client.tracingEnabled(false);
```
Once you run the dapp and started producing logs, go to zipkin client which is running on http://localhost:9411. There you can click RUN QUERY button without any filters to show all the logs.

FAQs

What is @web3api/tracing-js?

Is @web3api/tracing-js well maintained?

Last updated on 14 Feb 2022

Did you know?

Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.

Install