go-script-bash
go-script-bash copied to clipboard
mbland
Framework for writing modular, discoverable, testable Bash scripts
Per mbland/custom-links#138, functions from [`scripts/serve`](https://github.com/mbland/custom-links/blob/e1e6a656ca4e64842200472e964f9054e1df8115/scripts/serve) and [`scripts/lib/config-json`](https://github.com/mbland/custom-links/blob/e1e6a656ca4e64842200472e964f9054e1df8115/scripts/lib/config-json) may prove useful to import into `lib`.
Now that [bats-core/bats-core](https://github.com/bats-core/bats-core) development is progressing apace, and it already incorporates my optimizations (bats-core/bats-core#8), I'll update the `_GO_BATS_URL` and `_GO_BATS_VERSION` in `lib/bats-main` once a bats-core release is tagged.
The `[email protected]` function could be made generic to display any set of environment variables, including those currently printed by `./go vars`. This feature will require some thought, and won't be...
Not sure I want to turn all or parts of [unofficial Bash strict mode](http://redsymbol.net/articles/unofficial-bash-strict-mode/), but it's a very interesting idea.
Once the `./go null` command from #190 is released as part of [v1.7.0](https://github.com/mbland/go-script-bash/milestone/5?closed=1), the tests for `go-template` can be updated to use it. It can't happen before then since the...
Now that the plugin protocol is complete per the merging of #136 and closing of #120, there should be a new `./go plugins install` subcommand to automatically and recursively install...
There could be a generic mechanism for an application to delegate to a specific plugin, such that it adopts the help text of a plugin script or module automatically. Basically,...
This will be important for plugin compatibility. Already have a sketch implementation in-hand.
Adding the following to `go-core.bash` would avoid some nasty surprises: ```bash if [[ "$OSTYPE" == 'msys' ]]; then export MSYS_NO_PATHCONV='true' export MSYS2_ARG_CONV_EXCL='*' fi ``` per: [How to stop mingw and...
Per #173, we should automatically generate module function summary documentation as part of `./go modules -h ` to avoid the problem of out-of-sync header comments altogether.