@web3api/client-js: Added getManifest(...), getFile(...), and getSchema(...) methods to the client, simply provide a URI.
@web3api/cli: APIs can now define metadata via the web3api.meta.yaml manifest file. Upon compiling your project, the CLI will copy all referenced metadata files into the build directory. Applications such as The Polywrap Hub will use this metadata file to display details about your package such as: title, description, icon, example queries, etc.

Bugs

@web3api/schema-parse: Duplicate fields on object & query types are not detected, and will cause a compiler error.

Breaking Changes

@web3api/client-js: Removed the loadWeb3Api(...) method from the client. This is because we do not want to give the user of the client a direct reference to the underlying API class object. Since garbage collection will delete these, having the user able to hang onto references, will result in them staying in memory.

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 04 Sep 2021

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