Skip to content
This repository has been archived by the owner on Jul 15, 2023. It is now read-only.

Issues with intentional backslashes in the no-octal-literal rule. #413

Closed
iclanton opened this issue Jan 31, 2018 · 1 comment
Closed

Issues with intentional backslashes in the no-octal-literal rule. #413

iclanton opened this issue Jan 31, 2018 · 1 comment
Labels
Difficulty: Medium People with non-trivial experience in TSLint should be able to send a pull request for this issue. Resolution: Fixed Hooray! Type: Bug
Milestone
5.1.0

Comments

@iclanton
Copy link
Member

I've noticed that the no-octal-literal rule flags strings with intentionally escaped backslashes (i.e. - "\\1" -> \1) get incorrectly flagged by the no-octal-literal rule.

I put together a fix: #412
@HamletDRC HamletDRC added this to the 5.0.4 milestone Apr 16, 2018
@HamletDRC
Copy link
Member

closed with #412

@JoshuaKGoldberg JoshuaKGoldberg added Difficulty: Medium People with non-trivial experience in TSLint should be able to send a pull request for this issue. Resolution: Fixed Hooray! labels Jul 19, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
Difficulty: Medium People with non-trivial experience in TSLint should be able to send a pull request for this issue. Resolution: Fixed Hooray! Type: Bug
Projects
None yet
Milestone
5.1.0
Development

No branches or pull requests
3 participants
@HamletDRC @JoshuaKGoldberg @iclanton