Indentation of code with a multiline tagged template literal string seems off

[nerdo]

What version of standard?
12.0.1

What operating system, Node.js, and npm version?
macOS Mojave 10.14.1
Node.js 10.11.0
npm 6.5.0

Input file test.js

/* global describe, test, expect */
import { setupCustomMatchers } from '../helpers/jest'
import { SupervisorInterface } from './SupervisorInterface'
import { Supervisor } from '../Supervisor'

setupCustomMatchers(expect)

const newSupervisor = () => new Supervisor()

describe('SupervisorInterface conformance of', () => {
  test.each`
    concreteImplementationName | newInstance
    ${'Supervisor'}               | ${newSupervisor}
  `('$concreteImplementationName', ({ newInstance }) => {
    const supervisor = newInstance()
    expect(supervisor).toImplement(SupervisorInterface)

    let setPresenterResult
    expect(() => { setPresenterResult = supervisor.setPresenter(null) }).not.toThrow()
    expect(setPresenterResult).toBe(supervisor)
    expect(supervisor.getPresenter()).toBe(null)

    let setNextActionDelegatesResult
    const before = () => {}
    const after = () => {}
    expect(() => { setNextActionDelegatesResult = supervisor.setNextActionDelegates(before, after) }).not.toThrow()
    expect(setNextActionDelegatesResult).toBe(supervisor)
    expect(supervisor.getNextActionDelegates()).toEqual([before, after])
  })
})

What did you expect to happen?
Running standard on test.js reveals several indent errors, however, it seems to me that the indentation in the original file is correct.

For example, if one were to remove the tagged template literal altogether, it would be a normal function call and the indent errors disappear.

What actually happened?
Taking it one step further, running standard --fix on the file produces the following:

/* global describe, test, expect */
import { setupCustomMatchers } from '../helpers/jest'
import { SupervisorInterface } from './SupervisorInterface'
import { Supervisor } from '../Supervisor'

setupCustomMatchers(expect)

const newSupervisor = () => new Supervisor()

describe('SupervisorInterface conformance of', () => {
  test.each`
    concreteImplementationName | newInstance
    ${'Supervisor'}               | ${newSupervisor}
  `('$concreteImplementationName', ({ newInstance }) => {
  const supervisor = newInstance()
  expect(supervisor).toImplement(SupervisorInterface)

  let setPresenterResult
  expect(() => { setPresenterResult = supervisor.setPresenter(null) }).not.toThrow()
  expect(setPresenterResult).toBe(supervisor)
  expect(supervisor.getPresenter()).toBe(null)

  let setNextActionDelegatesResult
  const before = () => {}
  const after = () => {}
  expect(() => { setNextActionDelegatesResult = supervisor.setNextActionDelegates(before, after) }).not.toThrow()
  expect(setNextActionDelegatesResult).toBe(supervisor)
  expect(supervisor.getNextActionDelegates()).toEqual([before, after])
})
})

Thoughts
This only seems to apply to multiline tagged template literals. If one changes test.js and puts the tagged template literal on one line, it behaves as expected... as if it were just a simple function call. Clearly, the indentation of the template literal is affecting the indent rule.

I believe this is a problem with eslint. I have, in fact, run into the same issue with it using just eslint in the past and was able to fix it adding this to my .eslintrc (https://stackoverflow.com/a/53094449/2057996):

"indent": [{ "ignoredNodes": "TemplateLiteral > *" }]

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.