Key validation #219
Merged
Key validation #219
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
|
@matthope1 is attempting to deploy a commit to the reworkd Team on Vercel. A member of the Team first needs to authorize it. |
4 tasks
|
The RegExp used Valid keys that are failing: "The keys from open ai have 51 characters in total" not sure this is true anymore, all new keys I get are 56 characters in total. but that might change in the future. I have created a PR to use |
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.
Added Key validation to the setup script.
The keys from open ai have 51 characters in total and are prefixed with "sk-".
So this regex captures that case ^sk-[a-zA-Z0-9]{48}$
I've also added the same check within the settingsDialog component & It won't save an API key unless it has a valid format.
It will also notify the user with an alert.