I noticed this as well. Example code that works as expected:

function example () {
  const router = reverse`
    GET /example greet
  `({
    greet () {
    }
  })
}

But once I add a parameter to the template string, like so:

function example () {
  const router = reverse`
    GET /example/${id} greet
  `({
    greet () {
    }
  })
}

[email protected] suggests that it should instead format it without the indention in the object literal:

function example () {
  const router = reverse`
    GET /example/${id} greet
  `({
  greet () {
  }
})
}

which seems wrong. (This might be a bug in eslint!) An example of the error reported follows:

  /path/to/file:37:1: Expected indentation of 2 spaces but found 4. (indent)
  /path/to/file:38:1: Expected indentation of 2 spaces but found 4. (indent)
  /path/to/file:39:1: Expected indentation of 0 spaces but found 2. (indent)

Bug still exists with standard v12

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

This appears to be a bug in ESLint. Has anyone filed an issue on ESLint for this yet?

I think eslint/eslint#10932 describes the same bug.

Okay, until ESLint fixes this, let's just disable indentation checking on children of template literals.

I'm going to add this exception to the indent rule: "ignoredNodes": ["TemplateLiteral > *"]

This will be released in standard v14.