Several scripts had positional parameters that it'd be nice to have back
Why?
Positional parameters, particularly for one parameter commands, are convenient
What-should happen?
This should only be done afterhttps://github.com/mrlunchbox777/basic-setup/issues/117
After moving to standardized parameters and help documentation in the bash scripts, positional parameters were dropped. If possible, it'd be nice to have these back. This also depends on golang's support for positional parameters.
There are several commands that might benefit from this, but they include how, kgp, kgpbl, etc. Part of this task would be to identify those that it would make sense to have positional parameters, and then enable them for those commands.
Code of Conduct
[X] I agree to follow this project's Code of Conduct
Contact Details
mrlunchbox777@gmail.com
Feature Description
Several scripts had positional parameters that it'd be nice to have back
Why?
Positional parameters, particularly for one parameter commands, are convenient
What-should happen?
This should only be done afterhttps://github.com/mrlunchbox777/basic-setup/issues/117
After moving to standardized parameters and help documentation in the bash scripts, positional parameters were dropped. If possible, it'd be nice to have these back. This also depends on golang's support for positional parameters.
Covers this TODO
Steps to Test
There are several commands that might benefit from this, but they include how, kgp, kgpbl, etc. Part of this task would be to identify those that it would make sense to have positional parameters, and then enable them for those commands.
Code of Conduct