-
Notifications
You must be signed in to change notification settings - Fork 51
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
[lint] Remove no-control-regex #1258
Merged
Merged
Changes from 2 commits
Commits
Show all changes
4 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -16,8 +16,20 @@ | |
|
||
import * as vscode from 'vscode'; | ||
|
||
// NOTE ASCII characters have codes ranging from u+0000 to u+007f | ||
// NOTE | ||
// | ||
// u+0000-u+001f: control ascii codes, ascii (ALLOWED) | ||
// u+0020-u+007f: printable ascii codes, ascii (ALLOWED) | ||
// u+0080-u+00ff: extended ascii codes, extended ascii (NOT ALLOWED) | ||
// | ||
// By experience, Linux os takes all extended ascii characters(u+0000-u+00ff) for passwords, even | ||
// controll asciis. whereas 'eslint' recommends not using regex including control ascii codes. | ||
dayo09 marked this conversation as resolved.
Show resolved
Hide resolved
|
||
// Therefore, we allow users to put control ascii codes. | ||
// | ||
// By experience, the passwords including extended ascii characters are not working when loging in | ||
// to remote vscode. Therefore, here we allow only 'ascii characters'(0x00-0x7f). | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. @jyoungyun I tried several tests under what you've mentioned, I summarized here what I've found out. It seems that leaving the codes as-is is enough for now. PTAL :-D |
||
function containsNonAscii(str: string): boolean { | ||
// eslint-disable-next-line no-control-regex | ||
return !/^[\u0000-\u007f]*$/.test(str); | ||
} | ||
|
||
|
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.
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.
I put this above 'no-extra-semi' to avoid possible merge conflict