Skip to content
This repository has been archived by the owner on Mar 25, 2021. It is now read-only.

no-string-literal: correctly fix property names with leading underscores #3184

Merged
merged 1 commit into from Aug 31, 2017
Merged

no-string-literal: correctly fix property names with leading underscores #3184

merged 1 commit into from Aug 31, 2017

Conversation

ajafff
Copy link
Contributor

@ajafff ajafff commented Aug 30, 2017

PR checklist

Overview of change:

The AST contains the escaped name. That bug is fixed in typescript@2.5.0. This adds a fix for older versions.
Fixes: #2965

Is there anything you'd like reviewers to focus on?

CHANGELOG.md entry:

[bugfix] no-string-literal correctly fix property names with leading underscores

The AST contains the escaped name. That bug is fixed in typescript@2.5.0. This adds a fix for older versions.
Fixes: #2965
@ajafff ajafff merged commit 729694e into palantir:master Aug 31, 2017
@ajafff ajafff deleted the bugfix/no-string-literal branch August 31, 2017 18:07
HyphnKnight pushed a commit to HyphnKnight/tslint that referenced this pull request Apr 9, 2018
…res (palantir#3184)

The AST contains the escaped name. That bug is fixed in typescript@2.5.0. This adds a fix for older versions.
Fixes: palantir#2965
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

field like "__xxx__" is not fixed correctly.
2 participants