Skip to content
This repository was archived by the owner on Jul 15, 2023. It is now read-only.
This repository was 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
Closed
Issues with intentional backslashes in the no-octal-literal rule.#413
Labels
Difficulty: MediumPeople with non-trivial experience in TSLint should be able to send a pull request for this issue.Resolution: FixedHooray!Type: Bug
Milestone
5.1.0
@iclanton

Description

@iclanton
iclanton
opened on Jan 31, 2018

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    Difficulty: MediumPeople with non-trivial experience in TSLint should be able to send a pull request for this issue.Resolution: FixedHooray!Type: Bug

    Type

    No type

    Projects

    No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions