mbland / go-script-bash

Framework for writing modular, discoverable, testable Bash scripts

ISC License

95 stars 16 forks source link

Improve plugin protocol #120

Closed mbland closed 7 years ago

mbland commented 7 years ago

Now that I'm trying to write a separate plugin, I'm hitting some rough edges. Basically, I'd like plugins to potentially be standalone programs, but that collides with some presumptions the core framework makes regarding command and module lookup paths. The solution here may overlap with #118.

mbland commented 7 years ago

126, #128, #130, #135, and #136 have effectively implemented the new protocol, which is very similar to npm's `node_modules` schema. Plugins can be nested arbitrarily deep, with command script, module, and plugin lookup paths scoped correctly at every level in the hierarchy.

Next steps would be to document the protocol and write a tool to automatically install plugins. But the semantics of the protocol are themselves done, so this issue is closed and I'll file new ones.

mbland / go-script-bash

Improve plugin protocol #120

126, #128, #130, #135, and #136 have effectively implemented the new protocol, which is very similar to npm's node_modules schema. Plugins can be nested arbitrarily deep, with command script, module, and plugin lookup paths scoped correctly at every level in the hierarchy.

126, #128, #130, #135, and #136 have effectively implemented the new protocol, which is very similar to npm's `node_modules` schema. Plugins can be nested arbitrarily deep, with command script, module, and plugin lookup paths scoped correctly at every level in the hierarchy.