Jure Granić Skender

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`,...

Allow user to get plugin config from client

3

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

Client config builder

1

Works towards resolving #1122 1st implementation of Client Config Builder. Very basic, follows the config logic that’s already present within the Client. Future work: - Set up config bundles for...

Add a `polywrap manifest` command/set of commands within the CLI. `polywrap manifest schema` - should print out the schema for the polywrap manifest file - should print out the schema...

Currently, while developing WASM wrappers, the only way to know whether we are writing the wrapper properly is to attempt a build of the wrapper. Working with large wrappers is...

**Is your feature request related to a problem? Please describe.** Currently we have no test coverage of our newly created `Logger` found inside the `polywrap` package. **Describe the solution you'd...

**Is your feature request related to a problem? Please describe.** `codegen` for plugins appears to also output the plugins ABI into a `./build` folder. This seems counter-intuitive, as the user...