-
Notifications
You must be signed in to change notification settings - Fork 0
Error handling #16
Copy link
Copy link
Open
Labels
Help wanted 🙌I'm desperate, please help a poor soul.I'm desperate, please help a poor soul.Priority: Medium 🌪️You should probably go take a look. Maybe this week still?You should probably go take a look. Maybe this week still?Type: Enhancement ⏫Somebody says your code could be better! And they're probably right.Somebody says your code could be better! And they're probably right.
Metadata
Metadata
Assignees
Labels
Help wanted 🙌I'm desperate, please help a poor soul.I'm desperate, please help a poor soul.Priority: Medium 🌪️You should probably go take a look. Maybe this week still?You should probably go take a look. Maybe this week still?Type: Enhancement ⏫Somebody says your code could be better! And they're probably right.Somebody says your code could be better! And they're probably right.
I really dislike the way Voyager takes care of errors. For example checking if
dbGuildhas an error or not every time is annoying, There has to be a better way to treat any kind oferrororexceptionor whatever. Like a general "Any and every error should be treated like the following" rule, but I doubt something like this exists.Basically, take a look at all the errors that might occur while using the bot, and try to handle them in the best way possible.