Closed belak closed 2 years ago
Would be nice to have an option to specify a template folder. I'm not interested in generating schemes for all the possible templates. As a user what I do want is to do something like base16-builder-go --path=./my-template
This would also make it easier to include base16-builder-go
as part of a pipeline step, where I could easily trigger a job to rebuild all the schemes for my template
Would be nice to have an option to specify a template folder. I'm not interested in generating schemes for all the possible templates. As a user what I do want is to do something like
base16-builder-go --path=./my-template
Yep! Version 0.10.0 of the spec recommends that builders focus on a single template rather than all of them. This PR defaults to building the current dir but also provides a --template-dir
option to build a different location.
This also adds embedded color schemes, making it even easier to release a binary version which will be useful to people out of the box.
It additionally bumps the required go version to 1.16.
I'm a little salty about the go.sum file, since without those changes we'd be dropping a few hundred lines of code.