Bug: `indent` is not reporting on wrong indentation

Environment

Node version: latest npm version: latest Local ESLint version: v8.6.0 Global ESLint version: n/a Operating System: Mac

What parser are you using?

Default (Espree)

What did you do?

Configuration

indent: [2, "tab"]

See demo

'use strict';

// https://262.ecma-international.org/11.0/#sec-isunclampedintegerelementtype

/* eslint indent: [2, "tab"] */

module.exports = function IsUnclampedIntegerElementType(type) {
	return type === 'Int8'
        || type === 'Uint8'
        || type === 'Int16'
        || type === 'Uint16'
        || type === 'Int32'
        || type === 'Uint32';
};

Note how the return correctly has a tab, but the || lines all have spaces. eslint does not warn on this.

What did you expect to happen?

eslint should warn on spaces being used for indentation, when configured to “tab”.

What actually happened?

No warning.

Participation

• I am willing to submit a pull request for this issue.

Additional comments

This definitely happened in eslint 7 also, and probably older versions.

[btmills]

The first version of indent was just about blocks and statements. We’ve since added on options for a whole bunch of multi line expressions. It seems reasonable to me that at some point along the way, the rule’s scope expanded to include all lines, not just blocks, statements, and a couple dozen other cases, which would make this an omission and plausibly justifiable a bug. Given that, I’m with @nzakas.

[nzakas]

Ok, marking as accepted. @ljharb feel free to open a PR.