wrap-cli
wrap-cli copied to clipboard
polywrap
Used to create, build, and integrate wraps.
# SLA - Polywrap Alpha ## Approval TODO: ratify this SLA, and all future updates, via DAO vote. ## Service Wrapper Persistence - Wrappers will remain online and available for...
- [x] polywrap/monorepo#741 - [ ] polywrap/monorepo#742 - [ ] polywrap/nodes#48
Currently the error handling in the IPFS & ENS plugins is very poor when doing URI resolution. Some conversation around this: "worst part right now is if ens or ipfs...
In the JS client + core libraries, we throw errors. This is a hard error handling method to develop against, because you do not know what functions will throw and...
When wrappers are loaded and invoked, client should output logs to the console. Like this `[Polywrap] Wasm Wrapper Loaded: wrap://...` There already is a tracer for zipkin and opentelemetry which...
JavaScript minimization (aka "minification") issues have been encountered in both the Uniswap v3 front end demo and the Polywrap Hub. For example, in the Polywrap Hub, class names were being...
Convert wrap.info to cuelang script with schemas for all the types and inputs, validate all the types and input before passing it to client.
Currently wrappers cannot access the system's `getRandomValues` interface. We should build a plugin to support this. More research & design is needed. Relevant links: https://docs.rs/getrandom/latest/getrandom/index.html https://docs.rs/getrandom/latest/getrandom/macro.register_custom_getrandom.html https://www.assemblyscript.org/stdlib/math.html#variants https://www.assemblyscript.org/concepts.html#special-imports https://www.w3.org/TR/WebCryptoAPI/#Crypto-method-getRandomValues https://developer.mozilla.org/en-US/docs/Web/API/Crypto/getRandomValues
Rust developers will expect to just be able to use `println!(...)`, instead of having to use the console wrapper, or `w3_debug_log` host function. We can potentially overwrite the `println!` macro...