wrap-cli

wrap-cli copied to clipboard

When developing a web application and using a wrapper that's locally available, or under development, one cannot use filesystem URIs as browsers have no access to the filesystem API. So...

namesty

Bug: deployment pipeline -> ipfs deployment -> 413 Request Entity Too Large

2

When trying to deploy the Uniswap V3 wrapper, I got this error. Deleting the `meta` folder and `polywrap.meta.json` resolved the issue.

krisbitney

moved here from https://github.com/polywrap/documentation/issues/113

krisbitney

moved here from https://github.com/polywrap/documentation/issues/112

krisbitney

moved here from https://github.com/polywrap/documentation/issues/111

krisbitney

moved here from https://github.com/polywrap/documentation/issues/110

krisbitney

moved here from https://github.com/polywrap/documentation/issues/109

krisbitney

moved here from https://github.com/polywrap/documentation/issues/108

krisbitney

I want Plugin URIs to be clearly defined, not arbitrarily

2

# 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...

dOrgJelli

I want wrapper schema base types to not include complex custom types (BigInt, JSON, etc)

2

# 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...

dOrgJelli