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

Fix several edge cases in the no-octal-literal rule. #412

Closed

Conversation

iclanton
Copy link
Member

  • The no-octal-literal rule ignored template strings
  • The no-octal-literal rule didn't match strings containing newline or tab characters
  • The no-octal-literal rule incorrectly matched escaped backslashes preceding numbers (i.e. - "\\1" matched when it shouldn't have)

@HamletDRC HamletDRC added this to the 5.0.4 milestone Apr 16, 2018
HamletDRC pushed a commit that referenced this pull request Apr 16, 2018
…receeded by an escaped backslash would fail the rule.

Fixing an issue where the no-octal-rule wouldn't handle template strings or newlines inside strings.

Fixing test numbering.

Fixing duplicate variable declaration.
@HamletDRC
Copy link
Member

@iclanton I pushed this... but the whole Octal rule is a little funky. It only looks inside strings for octal literals. The eslint rule looks into constants as well, which we don't do: https://eslint.org/docs/rules/no-octal

@HamletDRC HamletDRC closed this Apr 16, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants