By default, confirmation message will be deleted after the view is done whether with successful interaction or timeout.
Add delete parameter. This is to specify whether to delete the message after the view is done. For cleaner output, this defaults to True.
Update on_timeout. Message will be edited or deleted if .message attribute is assigned. There were cases where the .message attribute cannot be assigned directly (without additional API call). So in this case you may want to set a value for delete_after parameter when sending the message. Example:
Add resolve_default_keys parameter in .fetch(). This is to prevent KeyError due to some of the keys were not saved into the database. Happened in supportutils plugin before the temporary solution were made.
Add alias eutils for ext-utils command.
Update ext-utils reorder command:
Now the plugins that match the criteria will only be reordered if they were loaded before utils plugin.
Changelog
Update
ConfirmView
:delete
parameter. This is to specify whether to delete the message after the view is done. For cleaner output, this defaults toTrue
.on_timeout
. Message will be edited or deleted if.message
attribute is assigned. There were cases where the.message
attribute cannot be assigned directly (without additional API call). So in this case you may want to set a value fordelete_after
parameter when sending the message. Example:Update
Config
:resolve_default_keys
parameter in.fetch()
. This is to preventKeyError
due to some of the keys were not saved into the database. Happened insupportutils
plugin before the temporary solution were made.Add alias
eutils
forext-utils
command.Update
ext-utils reorder
command:utils
plugin.