-
-
Notifications
You must be signed in to change notification settings - Fork 406
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix: switch PGP regex to span multiple lines #1598
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You also need to update the regex for the private key in src/components/Settings/Notifications/NotificationsEmail.tsx
. 🙂
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, thanks for fixing this! 🙂 We should be able to get this merged as soon as @sct has a chance to review.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM :) Thanks for this!
@all-contributors please add @Jabster28 for code |
I've put up a pull request to add @Jabster28! 🎉 |
🎉 This PR is included in version 1.25.0 🎉 The release is available on:
Your semantic-release bot 📦🚀 |
Description
copying PGP keys from any PGP client almost never results in a single-lined key, and as such I don't think the input regex should require it all to be in one line, as the openPGP NPM module allows for whitespace in their keys.
Screenshot (if UI-related)
N/A
To-Dos
yarn build
yarn i18n:extract
Issues Fixed or Closed