Skip to content

Releases: polywrap/wrap-cli

Web3API 0.0.1-prealpha.46

08 Oct 03:45
d565bfe
Compare
Choose a tag to compare

Web3API 0.0.1-prealpha.46

Bugs

  • @web3api/core-js: Properly check for "undefined" values in query arguments.
  • @web3api/wasm-as: Improved MsgPack deserialization of integers (signed & unsigned).

Web3API 0.0.1-prealpha.45

23 Sep 12:40
b8a2364
Compare
Choose a tag to compare

Web3API 0.0.1-prealpha.45

Features

  • @web3api/tracing-js: Support service name configuration.

Web3API 0.0.1-prealpha.44

18 Sep 00:44
2b6245c
Compare
Choose a tag to compare

Web3API 0.0.1-prealpha.44

Features

  • @web3api/client-js: Use Fleek's IPFS gateway.

Web3API 0.0.1-prealpha.43

17 Sep 21:35
6e4d0c3
Compare
Choose a tag to compare

Web3API 0.0.1-prealpha.43

Features

  • @web3api/client-js: Added the client.subscribe(...) method, enabling users to easily send queries at a specified frequency.

Bugs

  • @web3api/tracing-js: Replaced the util-inspect dependency with a browser compatible one.

Web3API 0.0.1-prealpha.42

14 Sep 09:47
8d0721b
Compare
Choose a tag to compare

Web3API 0.0.1-prealpha.42

Bugs

  • @web3api/schema-parse: Removed unnecessary sanitization for imported methods without any arguments.

Web3API 0.0.1-prealpha.41

14 Sep 09:23
4a0bed3
Compare
Choose a tag to compare

Web3API 0.0.1-prealpha.41

Features

  • @web3api/schema-parse: Added support for JSON as a base type.
  • @web3api/ens-api: Merged in an initial version of the ENS Wasm based Web3Api.
  • web3api.build.yaml: Added support for the linked_packages property, allowing you to link local packages into the dockerized build-env.

Bugs

  • @web3api/schema-compose: Fixed an invalid GraphQL bug that occured when an imported query method did not have any arguments.

Web3API 0.0.1-prealpha.40

04 Sep 04:42
d8d46cd
Compare
Choose a tag to compare

Web3API 0.0.1-prealpha.40

Features

  • @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.

Web3API 0.0.1-prealpha.39

02 Sep 21:10
f655aa4
Compare
Choose a tag to compare

Web3API 0.0.1-prealpha.39

Features

  • @web3api/client-js: Added https://polywrap-dev.mypinata.cloud and https://ipfs.infura.io as default fallback IPFS providers.

Web3API 0.0.1-prealpha.38

31 Aug 21:49
6622ace
Compare
Choose a tag to compare

Web3API 0.0.1-prealpha.38

Breaking-Change

  • @web3api/client-js: Removed the usage of _w3_init, as it's unnecessary and caused issues with adding Rust-Wasm support.

Web3API 0.0.1-prealpha.37

27 Aug 01:40
075b2ee
Compare
Choose a tag to compare

Web3API 0.0.1-prealpha.37

Bugs

  • @web3api/asyncify-js: Fixed problem when Wasm modules are larger than 4 KB. More info here.
  • @web3api/client-js: Use new asyncify-js package, where instantiation is asynchronous.