oppia: Unexpected lint error when using "bypass" in a comment
Lint error The use of the word "bypass" is not allowed, particularly with regards to bypassSecurityTrustHTML() and similar functions in Angular. was thrown when “bypass” was used in a comment. This is unexpected. It should be possible to use the word in comments.
Helpful info to solve the issue:
- We can use the word “bypass” anywhere except for the following cases:
- Function
- Class
- All kinds of identifiers
- The lint check currently exists lint
general_purpose_linterfile (here), and it should either be modified or moved to third party linters to solve the issue.
About this issue
- Original URL
- State: closed
- Created 3 years ago
- Comments: 16 (15 by maintainers)
@DubeySandeep As per offline discussion, kindly leave a comment here verifying if need this regex check or not. Thanks!
@OBITORASU Sorry for delayed response. Appreciate the effort you have put to explore the solutions and explaining it. But I am not sure if the approach (i.e the regex modification) you are suggesting would be the correct way. @DubeySandeep would you like to loop in here? One plausible way could be to shift the check from the general purpose linter to individual third party linters because I think we could implement it more easily there as per our requirements.
Hi, I faced this when I added a comment in one of the e2e files.
@kevintab95 Can you please provide a link to the location or the file where you faced this error? @OBITORASU is interested to work on resolving this issue.
I have assigned myself to keep track of the issue.