wrap-cli
wrap-cli copied to clipboard
polywrap
Used to create, build, and integrate wraps.
This PR aims to fix an error on build when if we wanted to create an attribute that was a map, i.e: ```graphql type Data { total_market_cap: Map! @annotate(type: "Map!")...
Partially closes #1057 This PR performs the 1st steps of the refactor of the Polywrap project manifest files (wasm, interface, plugin, app). Things to note: - The loading of `polywrap.app.yaml`,...
tests fail in @polywrap/templates. There, `npx polywrap build` says that `wasm-as` doesn't export the new type. It seems to be using an unchanged version of `@polywrap/wasm-as`. I verified that the...
We should allow a wrapper to know about its URI. ~~Canonical uri of the wrapper should be read from wrap.info during codegen and exported as a constant in the bindings~~...
This PR modifies the Ethereum plugin's config to use a `Connections` store. The `Connections` class stores `Connection` instances. App developers can keep a reference to the Connections store and use...
Add "rename" feature to the annotate directive in GraphQL type. ```rust MarketData2(helloWorld=md1.hello_world) ``` ``` graphql type MarketData1 { hello-world: String! @annotate(rename="helloWorld", exclude=true) } type MarketData2 { helloWorld: String! } ```...
Closes #839 The implementation fetches the plugin config by calling its factory function within the PluginPackage and extracting the config from the resulting object.
Closes #1122 Possible future tasks: - [ ] `PolywrapClient` probably shouldn't know about `ClientConfigBuilder` and shouldn't know about `defaults`. Add issue? - Should remove the `noDefaults` option within the constructor...
Want to complete before merge: - [x] Tests for timeouts - [x] IPFS - [x] IPFS Resolver - [x] Determine what to do regarding IPFS Interface `fallbackProviders` - Should we...