Summary

The user should be given the chance to set input parameters in the UI when submitting a workflow from a template.

The work done in argoproj/argo#3498 is great, but it only works when (default?) values for the parameters have been set in arguments.parameters.

Instead I suggest both the list of inputs.parameters and arguments.parameters should be consider

Description

Many of the tests in https://github.com/spacemeshos/go-spacemesh/blob/develop/cmd/node/node_test.go use goroutines to run and interact with a process concurrently. They have require statements inside these goroutines, which is a no-no because when a require statement fails inside a goroutine it does not stop the test, in some cases causing tests to hang indefinitely. Here's one s

We should modify the code in dffml/cli/dataflow.py within the Diagram class to not show operation.inputs which have default values. It makes for giant diagrams sometimes. We should provide an option to show them again

Ideally, we'd take a page from the https://github.com/multiformats/js-multiformats book and support cjs, esm, etc builds via rollup and friends to support multiple platforms/use-cases. Since this is designed to be a light-weight alternative to other ipds-based libraries, it should have a really low barrier to usage out of the box. In fact, moving forward, this should be a pretty critical require