commando | Talon command cheat sheet

Is there a reason why you use ESM in your code? You can configure TypeScript to use CommonJS modules like this:

If I understand correctly, you want to delete all the messages that came from the user, and the bot, which would be the command, the response, the extra info you waited for, and but not that response? Well here you go, this just came quickly to my head, there could be a better way:

It seems, results[0] is not an instance of cardPack. It seems you're using fuse.js to search, and according to its examples it returns an array of objects that have the following keys: item, refIndex, and score.

It seems, item is the instance you're looking for, so try to modify cardPack to:

I handled this adding default property 'default': 'isempty' and then I catch it in the command's code. So, the code looks like it:

You can do it like this if you just want to remove the default commands but keep the default types and groups provided by commando.

If you can pass the client you can use the events.
Example:
index.js

If the problem is that you simply need to deal with the case where element.genre_ids is not defined in the API result, I think you could simply change the assignment of objectResults to be:

The simplest method is to assume that the SQL script was written in a reasonably readable manner and that there is either 1 statement-per-line or that statements are split over multiple lines and you will not have the case where there are multiple statements on a single line.

The majority of cases can be handled by:

Read the next line and trim any leading white-space:

• If it starts with SET or COLUMN then you have a SQL/Plus directive which will (typically) consist of a single line; that line is your statement.
• If it starts with CREATE FUNCTION, CREATE PROCEDURE, CREATE PACKAGE, DECLARE or BEGIN (and a following white-space character) then you will have a PL/SQL block that will be terminated with a / on a separate line and you can read lines until you have found it and that is your complete statement.
• If it starts with -- then it is a comment and you can skip the rest of the line and prepend it to the next statement (since comments are part of the next statement).
• If it starts with /* then it is an inline comment and you can read until the next */ and then repeat by processing the rest of the line (the comment will be prepended to the next statement).
• Otherwise, read until the next ; that is at the end of a line (or followed by a comment) (or / on a separate line) and that is your complete statement.

Then repeat, reading the next line.

This is not guaranteed to work on 100% of cases (i.e. if you have multi-line string literals which happen to have a ; at then end of a line within the literal). You should review the output to see if there are any additional cases that need to be handled but for relatively simple scripts it should work.

If you have developers that like writing (less readable) scripts with multiple statements on the same line then you may need to implement a parser.

I figured out my problem, I was not adding a value to the key, so in the end I got this: (added other things too)