dOrgJelli
dOrgJelli
Currently, most-all interface types for TypeScript applications are like so: ```typescript interface ModuleMethodInput extends Record { argument?: Types.String | null; } export const Module = { method: async ( input:...
Currently the rust codegen uses `String` instead of `str` for all of its types. This is needless, since these types should be expected to be "static" and immutable. An example...
# Motivation I want to be able to build Polywrap enabled apps in Go. This requires the creation of a Polywrap Client in Go. # Requested By * https://www.notion.so/polywrap/Pocket-999a8232a1c04987a621ab8dddffe1e2
If wrappers are being hosted on a central server, addressable using a DNS based domain through HTTP(S), we should support querying them through a new URI resolver + authority. For...
# Motivation Currently, plugin URIs are defined in a arbitrary way, which can easily break composability as the Polywrap development ecosystem grows and decentralizes. We should have tailored developer experience...
# Motivation Currently, we've included a few "complex" types within our list of schema base types. These [include](https://github.com/polywrap/monorepo/blob/42f7e0756a6b46d5a3e2264d9fd0c9e8a9f152da/packages/manifests/wrap/formats/abi/0.1.json#L488-L490): - BigInt - BigNumber - JSON This is a pattern that is...
closes: https://github.com/polywrap/toolchain/issues/1341
**Is your feature request related to a problem? Please describe.** Currently, integrators of wrappers do not have an easy way to determine if a wrapper will run successfully within the...
**Is your feature request related to a problem? Please describe.** When developers are building wasm wrappers with the `vm` build strategy, the only way to customize it is to modify...
# Motivation I want to be able to build Polywrap enabled apps in Rust. This requires the creation of a Polywrap Client in Rust. # Prior Work We already have...