Fixes for input re-prompting #107
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.
When prompting with readInt, readFloat, or readBoolean, correctly re-prompt the user with the output from the failing prompt
Summary
Input re-prompts weren't including the latest incorrect input in the prompt. This fixes that, as well as simplifying how
readNumberworks.readLinebehaves separately, since it doesn't have a parseFn, so I'm just duplicating the behavior of printing the prompt then output there.Changes:
Screenshots of the change:
Checklist
npm testpasses