Differentiate between wrong password and communication error #90
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
of the code were modified. This will help us understand any risks of integrating
the code.
Allow public access to checkPassword() to return one of
FINGERPRINT_OK,FINGERPRINT_PACKETRECIEVEERR,FINGERPRINT_PASSFAIL. Useful to determine if failure is due to wrong password or communication error.Also fix comment for
FINGERPRINT_PASSFAIL(0x13) to reflect the actual meaning as described in the datasheet:doesn't apply to a supported platform of the library please mention it.
Does not affect existing functionality.