This repository has been archived by the owner on Sep 20, 2024. It is now read-only.
Fail with better error when thread not found #1758
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
benbrown
approved these changes
Aug 2, 2019
|
Good change, thanks! |
benbrown
approved these changes
Oct 28, 2019
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Motivation
I was helping a friend debug a conversation earlier and the error we were getting didn't make any sense. Then we realized the thread name just had a typo in it.
Demo project with errors: comet-spice on Glitch.
Changes
Improves the following error message:
When trying to go to a thread that hasn't been defined, e.g.
convo.gotoThread('foo'):=>