powershell-command-executor icon indicating copy to clipboard operation
powershell-command-executor copied to clipboard
verified publisher icon bitsofinfo

Generalize command service functionality away from powershell only

Open bitsofinfo opened this issue 10 years ago • 2 comments

There are several things that can be done to make this more of a generic "shell agnostic" wrapper around stateless-process-command-proxy

  1. Support configurable function in constructor to handle argument sanitization
  2. Support configurable function in constructor to permit modifcation of all arguments, i.e. for PS commands the PSCommandService auto prepends a "-" to all argument names
  3. Rename to CommandService, get rid of PS

bitsofinfo avatar Feb 18 '15 23:02 bitsofinfo

Can this be used to run Powershell scripts, or is it just for commands ? Thanks.

gkhatib avatar Mar 26 '15 23:03 gkhatib

Sure, but I suggest you just use https://github.com/bitsofinfo/stateful-process-command-proxy instead (the lower level module). Create your custom powershell script then invoke it via that. This project (powershell-command-executor) is for a registry of pre-defined commands, see the README for details.

bitsofinfo avatar Mar 26 '15 23:03 bitsofinfo