Fix superuser password verification undefined issue #22
Conversation
This file contains hidden or 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
Fixed the bug where password confirmation validation showed
'answer?.password undefined' error. Changed the type annotation
from restrictive `{ password?: string }` to `any` to properly
access the password field from inquirer's answers object.
The issue was that the type annotation was too narrow and didn't
match the actual structure provided by inquirer's validate callback.
The previous fix didn't work because the answers parameter was null. This commit implements a more robust solution by storing the password in a variable (enteredPassword) when it's first validated, then comparing the confirmation input against this stored value directly. This approach doesn't rely on inquirer passing previous answers to the validate callback, making it more reliable across different inquirer versions.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Fixed the bug where password confirmation validation showed
'answer?.password undefined' error. Changed the type annotation
from restrictive
{ password?: string }toanyto properlyaccess the password field from inquirer's answers object.
The issue was that the type annotation was too narrow and didn't
match the actual structure provided by inquirer's validate callback.