Issues Labeled as new_feature
#176## Description - Support 1build for Windows - Os ## Acceptance Criteria - Able to use all functionality of 1build on Windows OS - Run tests on Windows platform (on CI/CD Travis CI or GitHub Actions)
#167## Description - We want a developer to have the ability to work with 1build - just from the command line (and with 1buil commands) - Currently, `1build` support init command - which initializes the project configuration - Same way - we want to have the ability to delete the project configuration - Ask for consent before deleting the file (If not given by command) - Ability to pass consent by command itself ## Example 1. `1build delete` - ASK for consent (yes or no) 2. `1build delete --force` 3. `1build delete -f` ## Acceptance Criteria - `1build delete` / `1build d` - should ask for consent to delete (y/N) - The default option will be `N` - Upon input `n` OR just enter(which by default is NO) - should NOT delete the file. - Upon input `y` - should delete the file. - Should not ask for consent (instead, give an error) - If file not present
#140## Description Sometimes developers choose to not see all logs/output of your command and just see `success` or `failure` as the outcome. Hence adding `--quite` or `-q` flag to 1build command execution will result in just executing the command but not showing the entire output of it. ## Acceptance Criteria - Ability to pass `quiet` or `-q` flag to command execution. ex - ```bash 1build test --quiet 1build test -q ``` - If flag present - then just print `SUCCESS` (if exit code of the command is `0`) - If exit code is not zero - print failed command logs with – `FAILURE` message & exit code - Do not print logs for successful commands Example: in commands `1build test lint build` if test and lint succeed and build failed. Do not print logs from `test` and `lint` but only print logs of `build` command that failed.