Fixing ReferenceError in catch block

[C-Doug-iS]

Sending error to channel results in a ReferenceError because cleaned is not defined in the catch block's scope.

Replaced with sending the error's stack to resolve this.

[thetayloredman]

1. This doesn't send the actual error.
2. err.stack is string[]? meaning it could be undefined.

[RealShadowNova]

1. This doesn't send the actual error.
2. err.stack is string[]? meaning it could be undefined.

1. Error#stack does send the actual error message, plus the error stack.
2. Technically err is of type unknown, so an instance check for Error would be appropriate here, but the chances of a non-error type being thrown is unlikely.

[thetayloredman]

@RealShadowNova... oops; implementation issue with the way my stack system works. soz!

[thetayloredman]

can you screenshot what actually happens?

[C-Doug-iS]

            message.channel.send(`\`ERROR\` \`\`\`xl\n${cleaned}\n\`\`\``);
                                                        ^

ReferenceError: cleaned is not defined

As cleaned is not defined in the catch block, a ReferenceError is thrown. Error#stack lazily generates a string, which to the best of my knowledge should always be populated once accessed.

You could always just send the plain Error, but that will not provide any information regarding the actual location of the error, just the type and message associated with it.

[thetayloredman]

this needs to be merged lmao

[migue802]

Bump - why this isn't merged yet

[Chicken]

Because the guide, the bot, and the community are pretty much dead.