Feature Request - Cron schedule - Allow command argument entry
veteranmina opened this issue · comments
Currently in the schedule if a command has the optional argument parameter available this can be called in the background only via terminal.
In some circumstances one may wish to have more updates done i.e. notifications and other argument available commands. To do this would mean changing the frequency of the esi:update:notifications command which would cause unneeded taxed resources on both the SeAT instance and ESI. Allowing argument entry would reduce the amount of calling needed and focus on the character/corporation(s) selected and more flexibility for management of specific character/corporation(s).
@veteranmina normally it's already possible. Command drop-down will list you only available commands. However, if some of them might (or must) have ARGS, you can fill the drop-down list manually (directly using the search box).
As an example, type esi:update:notifications 73738374727 and select it when it's displayed in the list.
Attempting to add an argument i.e. (esi:update:notifications 96190383) and selecting to save produces the error message "The selected command is invalid." not allowing this.