go-script-bash
go-script-bash copied to clipboard
mbland
Framework for writing modular, discoverable, testable Bash scripts
This is especially desirable for standalone programs.
While it's possible to use `${_GO_CMD_NAME[@]}` manipulations now, it'd be so much better if there were already core functions for that sort of thing.
Inspired by the need for `@go.join` and `@go.split` per #62, #81, and commit 99ab7805e6ef0a14568d8a100eec03bb2cb03631. All these deep technical reasons should not get lost to the sands of commit log history,...
After working a bit with traps as part of `@go.log_command` and in `tests/assertions`, it occurs to me it might be helpful to produce a `trap` module that helps command scripts...
Thinking about the upcoming JSON support and how to handle `@go.log_command` output, I'm thinking of emitting each line as something like: ```json {"d":_GO_LOG_COMMAND_DEPTH,"o":"line of output"} ``` It may also be...
Should be relatively straightforward to add by replacing the default `TIMEFORMAT` from: ```bash $'\nreal\t%3lR\nuser\t%3lU\nsys%3lS' ``` with something like this in `@go.log_command_invoke`: ```bash TIMEFORMAT='real %3lR user %3lU sys %3lS' ``` to...
The first implementation of `demo-core` (#57) will provide a list of available subcommands whenever it's actually executed, rather than one of its subcommands. When the argument list is empty, it's...
Thinking about #35 and researching options, I'm thinking it might not be too difficult to write a pure Bash [JSON](http://json.org) parser/emitter module. It would probably borrow much of the interface...
After integrating #44, some `readonly` variables that may be initialized with user-defined values must be set _before_ calling `. "$_GO_USE_MODULES"`. There needs to be better documentation of this pattern and...
Per @JohnOmernik, once #38 is decided and implemented, we may wish to create an interactive command to help produce the `log` module config file. This will happen after v1.3.0.