@web3api/manifest-schemas
Advanced tools
Changelog
Web3API 0.0.1-prealpha.74
@web3api/schema-bind
: Fix incorrect export from plugin-ts
bindings.Changelog
Web3API 0.0.1-prealpha.72
BigNumber
Schema Type: The BigNumber
type is now available for use as a base type for Web3API schemas.@web3api/cli
: w3 query ...
command now supports the following options:
-o, --output-file
: Output file path for the query result.-q, --quiet
: Suppress output.@web3api/schema-bind
: wasm-as
bindings have been updated to include a helper function requireEnv()
, which can be used to check if the environment is null or not.@web3api/templates
: The AssemblyScript & interface templates used for the w3 create api ...
command has been updated to include metadata (descriptions, icons, etc).@web3api/templates
: The AssemblyScript template used for the w3 create api assemblyscript ...
command has been updated to include e2e tests.Changelog
Web3API 0.0.1-prealpha.71
@web3api/client-js
: The Web3ApiClient
now has a public method loadUriResolvers()
, which will pre-fetch all URI resolver implementations.@web3api/client-js
: Custom URI resolver implementations now no longer cause an infinite loop during URI resolution.Changelog
Web3API 0.0.1-prealpha.70
@web3api/core-js
: Fixed the manifest migration script for web3api.meta
from v1 to v3. The name
property is now migrating properly to displayName
.Changelog
Web3API 0.0.1-prealpha.69
Map<K, V>
schema base-type has been added.__w3_subinvokeImplementation
host import. This now gives us a specific import function for these sort of invocations, which can allow for additional types of verification features to be added by clients.@web3api/schema-bind
: Add support for getImplementations
capability in TypeScript plugin (plugin-ts
) codegen.@web3api/schema-bind
: The schema-bind
project is now "module agnostic" and accepts an array of arbitrary modules, which it will pass directly to the different binding projects (wasm-as
, plugin-ts
, app-ts
, etc).@web3api/manifest-schemas
: Added the name: string
property to the web3api
manifest.@web3api/manifest-schemas
: Renamed web3api.meta
's name
property to displayName
.@web3api/manifest-schemas
: Added the tags: string[]
property to the web3api.meta
manifest, allowing wrapper to developers to add tag keywords to their package's metadata, helping improve searchability on package indexers like The Polywrap Hub.@web3api/ethereum-plugin-js
: Changed all instances of the chainId
property's type to BigInt
from UInt32
.@web3api/ethereum-plugin-js
: Added getBalance
to the Query
module, allowing callers to check the native balance of arbitrary addresses.Map<K, V>
schema base-type will break forward compatability of Polywrap clients.
@web3api/client-js
getImplementations
capability for interfaces will now require the following host imports: __w3_subinvokeImplementation
, __w3_subinvokeImplementation_result_len
, __w3_subinvokeImplementation_result
, __w3_subinvokeImplementation_error_len
, __w3_subinvokeImplementation_error
@web3api/wasm-as
, @web3api/schema-bind
, @web3api/cli
, @web3api/client-js
@web3api/schema-bind
: The entry point function's input & output types have changed.@web3api/cli
: The type of the expected export from user-defined codegen scripts has changed from:generateBinding = (
output: OutputDirectory,
typeInfo: TypeInfo,
schema: string,
config: Record<string, unknown>
) => void;
to
generateBinding = (
options: BindOptions
) => BindOutput;
@web3api/client-js
: User-configured interface implementations now extend the default configuration's, instead of overwritting them.Changelog
Web3API 0.0.1-prealpha.67
w3 app codegen
command, which generated types based on the apps wrapper / plugin integrations. For an example of how this works, see the updated application template projects by running w3 create app typescript-node my-app
or w3 create app typescript-react my-app
.@web3api/react
: Added the useWeb3ApiInvoke
hook as a non-graphql alternative to useWeb3ApiQuery
.@web3api/schema-compose
: Importing all dependency types from a schema import schema statement can now be done through the new wild-card syntax: #import * into Namespace from "w3://authority/path"
.@web3api/cli
: w3 build
CLI command now requires the use of the --manifest-file <path>
option in order to specify a custom build manifest file path.@web3api/cli
: w3 codegen
CLI command option renaming:
-m, --manifest-path <path>
to -m, --manifest-file <path>
-c, --custom <path>
to -s, --script <path>
-o, --output-dir <path>
to -c, --codegen-dir <path>
@web3api/cli
: w3 plugin
CLI command option renaming:
-m, --manifest-path <path>
to -m, --manifest-file <path>