wrap-cli
wrap-cli copied to clipboard
polywrap
Used to create, build, and integrate wraps.
Based on #1100 Resolves #1131 - move workflow from core and client to cli - move workflow schema to polywrap manifest schemas
TODO: - move `plugin codegen` and `app codegen` to just `codegen` - move `--codegen-dir`, `--publish-dir`, and `--client-config` into manifest file? probably good for a new PR (needs discussion)
Create development releases whenever new commits are made to `origin-dev`. These can be used in other projects that depend upon the toolchain, like wrappers.io.
When workflow execution fails due to a syntax error in the workflow file, users should get an error message that helps them understand there is an issue with their workflow...
While the Workflows seem to work as expected, the CLI run command does not currently output helpful messages when things go wrong or right. For example, `undefined` is printed to...
The validation success/failure messages don't say which job they are associated with. Since jobs run in parallel, this is confusing. When validation fails, users should be informed which job or...
During workflow execution, when a wrapper throws an exception there should be a message telling the user which job or step failed along with the wrapper exception thrown. That way...
The validation success/failure messages don't say which job they are associated with. Since jobs run in parallel, this is confusing. parent issue: https://github.com/polywrap/monorepo/issues/984
Now that plugins have the `getManifest` method defined (when #1046 is merged), the client doesn't need to know if it is interacting with a plugin wrapper or a wasm wrapper
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...
