Denys Zariaiev

CLI `build` subcommand should check VCS dirty workdir state

1

The behaviour should be consistent with `cargo-publish` and `--allow-dirty` flag.

There are plenty of missing features that might block migration from Dockerfile-approach. Some of the features are trivial to implement, others might require extra work and refactoring. Builder: - [x]...

Dockerfile statements: ``` Dockerfile COPY hom* /mydir/ COPY hom?.txt /mydir/ ``` Should have equivalent cargo-wharf metadata: ```toml [package.metadata.wharf.builder] copy = [ { src = "hom*", dst = "/mydir/" }, {...

The file should be taken into account and have a consistent behaviour with Dockerfile frontend.

Display array of strings in package settings as separate inputs

2

Maybe it's reasonable? E.g. make a flag in config: ``` coffee config: someSetting: type: 'array' default: [ 'first value', 'second value' ] list: true # this one items: type: 'string'...