What is the enhancement in mind? How should it look and feel?
The basic idea would be that AceConsole would run the input to a registered chat command through SecureCmdOptionParse first (and then probably only if GetRunningMacro is not nil) before passing the input onto the addons command handler. This would allow users of ace addons to build macros that use conditional text to choose between options and expect them to work.
Please provide any additional information below.
A user recently asked if they could call my addon in a macro like "/addon [button:2] ThisOption; ThatOption". I gave them a script macro that would do the same thing, but then thought about SecureCmdOptionParse which I had only recently noticed. I can add this logic to my own addons registered command line handler, but it seems like it might be something worth building into the ace framework. It seems to me quite natural that users will experiment in trying to call addons this way while individual addon developers may not think of the scenario or may not know about SecureCmdOptionParse.
|stencil||May 26, 2011 at 11:20 UTC||Create|
- 1 comment
- Last updated
- Aug 09, 2012
- May 26, 2011
- New - Issue has not had initial review yet.
- Enhancement - A change which is intended to better the project in some way
- Medium - Normal priority.