Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix: explicitly handle track not found error #193

Merged
merged 2 commits into from
Apr 20, 2022

Conversation

aquelemiguel
Copy link
Owner

Closes #192.

Additionally, when handling errors, we can only create a response if we haven't responded yet. For instance, when creating a response on top of the "searching" response, it used to panic:

image

If the interaction has already been acknowledged, then we must edit the response instead. Added that check.

@aquelemiguel aquelemiguel merged commit 0bfd98c into main Apr 20, 2022
@aquelemiguel aquelemiguel deleted the track-not-found-error branch April 20, 2022 11:14
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
🐛 bug Something isn't working
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Do not fail silently when track is not found
3 participants