sigurdsvela/boot

A command line tool for quickly creating starting points for project based on templates

boot's Issues

Colorize output

Add option if notify to colorise output. Default to true.

Implement validation of symbol input

Syntax would be something like

{
  ...
  "options" : {
    "--my-symbol" : {
      "symbol" : "symbol-id",
      "format" : "id" // <---
    }
  }
  ...
}

Implemented formats should contain

id

\_?[a-zA-Z0-9\-\_]

_Can start with a _, rest must be alpha-numeric or - or __
This would then be used in symbols like --name in the wordpress templates

version

\d+?.\d+?.\d+?(\-\d+)?

Must the three digits, separated by a period, can contain a prepending - followed by at leas one digit

Implement "symbol" JSON format validator

Should only allow non empty, [a-zA-Z0-9-_] string, starting with [a-zA-Z]

When not specifying "-o" or "--out", the path is relative to the run directory of boot.

When not specifying -o, boot should try to create the template in the current directory, or notify the user that -o must be specified.

Remove the need to specify --template in 'boot new' call

So one may write

boot new wordpress-plugin

Looks better, reads better, is better..

Make code rubocop compliant

JSON schema validation does not generate errors on missing description in option entries

And in turn allows the following

{
  ...
  options : {
    "--option"  : { "files" : {} },
    "--option2" : { "values" : {} },
    "--symbol"  : { "symbol" : "symbol-name" }
  }
  ...
}

All missing the description field

Allow for making some options require other options in template.json's

{
  [...]
  "options" : {
    "--vcs" : {
      "description" : "Choose version control system"
      "values" : {
        "git" : {[...]},
        "svn" : {[...]}
      }
    }
    "--remote" : {
      "description" : "Set remote for VCS",
      "requires" : "--vcs",
      "files" : "set-up-remote-file",
      "symbol" : "remote-url"
    }
  }
  [...]
}

Allow setting config options through the 'boot config' command

Make boot automatically download templates

Make boot automatically download boot template form github.com/sigurdsvela/boot-templates

Do not print the pretty name, but the identifier name in 'boot template --list'

Now it would for example list the wordpress plugin template as 'WordPress Plugin' and not the desired wordpress-plugin

Fix error template error messages

1. Doing stuff loading text should not prepend the error message
2. It should say

- try 'boot new --help'
+ try 'boot template the-template'

Fix check for Directory/File

Fix the check when the boot command is ran, that checks if there is a file of that name, an wether or not said file is a file or a directory.

Add --verbose option to boot template command

As of now, it's always verbose. So very very verbose.

Implement various validates of symbol input to be use in templates

Should allow for writing

template.json

{
  [...]
  "options" : {
    "--symbol" : {
      "symbol" : "symbol-id"
      "format" : "[format]"
      "format-description" : "Must be present if the format is a regex"
    }
  }
  [...]
}

[format] should be the name of a built in format, or a regex, starting with ^ and ending with $. If a regex, a format-description is required. This is to print to the user if (s)he enters an invalid value.

The format description should be written in the format
Must [be/start with/end with/conatin/not contain] [...]

Rename __dummy-file__ __boot-dummy-file__

This to make sure there are not any conflicts