Login with NSEC and HEX private key formats. Proper errors. #66

Merged
b merged 5 commits from issue-45 into main 2024-05-24 08:35:33 +00:00
Owner
No description provided.
m added 2 commits 2024-05-22 10:22:24 +00:00
m added 1 commit 2024-05-22 10:31:05 +00:00
y reviewed 2024-05-24 02:32:31 +00:00
@ -310,1 +326,3 @@
toast.error('Invalid Input!')
// Check if maybe hex nsec
try {
// const privateKey = nip19.decode(inputValue).data as Uint8Array
Owner

Please remove not used code

Please remove not used code
m marked this conversation as resolved
@ -330,3 +359,3 @@
<TextField
onKeyDown={handleInputKeyDown}
label="nip05 login / nip46 bunker string / nsec"
label="nip05 login / nip46 bunker string"
Owner

Shouldn't nsec be one of the options?

Shouldn't `nsec` be one of the options?
Author
Owner

@b said that we should not display it so we do not encourage users to use it. But it is visible in the error message if user types in something wrong.

@b said that we should not display it so we do not encourage users to use it. But it is visible in the error message if user types in something wrong.
y marked this conversation as resolved
m added 2 commits 2024-05-24 06:52:47 +00:00
y approved these changes 2024-05-24 06:55:44 +00:00
b merged commit 9caba52f7d into main 2024-05-24 08:35:33 +00:00
b deleted branch issue-45 2024-05-24 08:35:33 +00:00
Sign in to join this conversation.
No reviewers
y
No Milestone
No project
No Assignees
2 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: sigit/sigit.io#66
No description provided.