[quotemark: backtick] Incorrectly flags string literals in export line

[ericbf]

Bug Report

• TSLint version: 5.14.0
• TypeScript version: Version 3.3.3333
• Running TSLint via: Atom
• Related issues: [quotemark: backtick] Incorrectly flags string literals that must use single/double quotes #4514

TypeScript code being linted

export * from "./some-module"

with tslint.json configuration:

{
    "rules": {
        "quotemark": "backtick"
    }
}

Actual behavior

The quotes get flagged (and changed to backticks if fix is enabled).

Expected behavior

The quotes should remain as double/single quotes, as typescript/ecma doesn't allow backticks here.

[ericbf]

Here's another example:

Code being linted

const array: SomeType<string, "hello"> = []
const obj: {
	"kebab-case": string
} = {
	"kebab-case": "value"
}

Actual behavior

const array: SomeType<string, "hello"> = []
//                            ~~~~~~~ [" should be `]
const obj: {
	"kebab-case": string
//      ~~~~~~~~~~~~ [" should be `]
} = {
	"kebab-case": "value"
}

Expected behavior

const array: SomeType<string, "hello"> = []
const obj: {
	"kebab-case": string
} = {
	"kebab-case": "value"
//                    ~~~~~~~ [" should be `]
}

Problem summary

1. The fixing/flagging here flags some things that when changed breaks typescript syntax and doesn't flag other instances where it should be flagged.
2. Typescript required that the string literal type passed to the generic type be single/double, but the implementation of the backtick rule does not make that distinction. Seems that node doesn't have a clear-cut type though to exclude it.
3. For the type definition, the kebab case property name has to remain single/double quotes, or typescript breaks as well. What is the associated node type there? Mucking in the code trying to PR for this, seems that the type definition property name here doesn't have a clean-cut node type either.
4. The string literal in the property value assignment is not flagged, but it should. Seems that looking at the parent node ("kebab-case": "value") gives you "PropertyAssignment" for both the property key and the property value, while the key should be ignored in this case, the value should not. How would one implement this part when they don't have their own node types?

[ericbf]

Actually, I think I got something. PR soon.