Fix failure where launch type command is found and can't sync. #4
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When we try to sync existing commands, it will iterate through the ones returned and already recognised by this discord app, and may return command such as
launch
- which has a type/index of 4. This goes out of range, so crashes the parse command when it tries to set this within a map that doesn't exist.For now the simple solution will be to just put a null check on that array index in case you get any unknown command types come back - eg, new features that have come along since this library was written, as is the case here.
But It would also be a good idea to not only have these checks, but update the library to use the latest ApplicationCommandType definitions that include these new unrecognised types.