no-unexpected-multiline and template literal with typescript

[quolpr]

Tell us about your environment

• eslint 6.9.0
• node v11.6.0
• npm 6.9.0
• typescript 3.3.4

What parser (default, Babel-ESLint, etc.) are you using?

Not sure. I use CRA 3 without ejecting.

Please show your full configuration:

Configuration

{
  "extends": "react-app"
}

What did you do? Please include the actual source code causing the issue, as well as the command that you used to run ESLint.

function myTag<T>(...args): any {
  return undefined;
}

export const test = myTag<{
  field: boolean;
}>`
  test;
`;

The command:

eslint --ext js,ts,ts,tsx src

What did you expect to happen?

No eslint warnings will be raised

What actually happened? Please include the actual, raw output from ESLint.

./src/test.ts
  Line 5:  Unexpected newline between template tag and template literal  no-unexpected-multiline

But with

function myTag<T>(...args): any {
  return undefined;
}

export const test = myTag<{ field: boolean }>`
  test;
`;

No warnings are showing.

It especially frustrates when you are using styled-components and component have a lot of props, that will not fit the maximum line length.

[eslint-deprecated]

Unfortunately, it looks like there wasn't enough interest from the team
or community to implement this change. While we wish we'd be able to
accommodate everyone's requests, we do need to prioritize. We've found
that issues failing to reach accepted status after 21 days tend to
never be accepted, and as such, we close those issues.
This doesn't mean the idea isn't interesting or useful, just that it's
not something the team can commit to.

Thanks for contributing to ESLint and we appreciate your understanding.

[hardfist]

same issue, prettier will automatic format

export const test = myTag<{ field: boolean }>`
  test;
`;

to

export const test = myTag<{
  field: boolean;
}>`
  test;
`;

which will cause eslint error, which is verify frustrating

[kaicataldo]

Sorry this is so late - looks like this slipped through the cracks. Does this issue occur with the default parser? If not, this should probably be reported in the typescript-eslint repository.

@hardfist Prettier doesn't conform to ESLint's configuration, so if you're using Prettier for formatting you should turn any ESLint formatting rules off.

[mdjermanovic]

I believe this issue can be closed since it was fixed by #11698 (released in v6.7.2)

[aladdin-add]

Closing because there hasn't been activity for a few days. If it still occurs, please file a new issue. thanks!