Report #3044
vox ignores filter arguments when adding to chain
| source | e4tmyl33t |
|---|---|
| version | 0.1.1 |
| status | RES |
| priority | TRI |
| target fix | 0.3 |
| report date | 2023-09-21 00:43:57 |
| report | When adding a custom replace dictionary to local.db, if the "replace" output filter is not already active, you cannot load this custom dictionary directly via "@vox output replace ". You must first do "@vox output replace" to enable the filter, then "@vox output replace " to load the custom dictionary, before it will detect the custom dictionary and enable its use. Unsure if this is intended behavior or not. Additionally, there is no confirmation message when these custom dictionaries are loaded that indicate a successful application, which would be a nice addition for the future if possible. |
a year ago
armelthelae:
As it appears the above description swallowed anything between left- and right-carats I used for placeholders, to clarify: you cannot load this custom dictionary directly via "@vox output replace dictionaryname". You must first do "@vox output replace" to enable the filter, then "@vox output replace dictionaryname"
a year ago
rhet0rica:
Looks like a bug in the command parser for activating filters.
10 months ago
rhet0rica:
Turns out it just deletes the first word, not all the prompt. The syntax was intended to be '@vox <chain> <filter> add [<parameters>]' and vox wasn't prepared to deal with the fact that 'add' is optional in the final implementation.