Skip to content
This repository has been archived by the owner on Nov 16, 2023. It is now read-only.

request: error customization #2

Open
kyranet opened this issue Oct 2, 2020 · 0 comments
Open

request: error customization #2

kyranet opened this issue Oct 2, 2020 · 0 comments

Comments

@kyranet
Copy link
Member

kyranet commented Oct 2, 2020

Is your feature request related to a problem? Please describe.

Sometimes, admins may want to customize the error message Skyra sends, for example, in a slap command, the admin may want Skyra to send Who do you want to slap? when the argument fails to be resolved, instead of the generic You must provide a valid user.

Describe the solution you'd like

We can use #{str} inside tags, e.g:

{author} gave {user #{Who do you want to slap?}} a big slap! {random {url1} {url2} {url3} {url4}} (complementing #1).

Error messages are not affected by transformations - because they're not part of the output message, but an error.

It can also be weird if somebody did Echo: {string... #{Please specify the content} | bold | uppercase}, the admin expects this to return Echo: **SUCH WOW** when somebody runs it with s!mycommand such wow, but it's hardly expectable in the error itself - which would show **PLEASE SPECIFY THE CONTENT** if it did.

Describe alternatives you've considered

N/a.

Additional context

N/a.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant