Fix move command "No matching channels found" #445
Merged
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.
Bug Description:
In all the ways bot returns "No matching channels found" error even if the voice channel exists
Bug Cause:
the cause is using the custom Guild method
findMatchingChannels
which only supports text channels.Solution:
so I added another method called
findMatchingVoiceChannels
that can find voice channels too without touching the first to not break any functionality with other commandsPull Request recap:
Guild
calledfindMatchingVoiceChannels
that find voice channels starting from a channel mention