XO Documentation on overrides misleading

The docs show this structure:

{
	"xo": {
		"semicolon": false,
		"space": 2,
		"overrides": [
			{
				"files": "test/*.js",
				"esnext": false,
				"space": 3
			},
			{
				 "files": "test/foo.js",
				 "esnext": true
			}
		]
	}
}

But no matter how I formatted things, it never worked until I used this structure, with the “rules” property specified:

{
	"xo": {
		"semicolon": false,
		"space": 2,
		"overrides": [
			{
				"files": "test/*.js",
				"rules": {
					"esnext": false,
					"space": 3
				}
			},
			{
				"files": "test/foo.js",
				"rules": {
					"esnext": true
				}
			}
		]
	}
}

I think the docs need to be updated to reflect that

[pvdlg]

@simonhaenisch that’s normal, because no-console is a rule, so it should be under rules (whether it’s an override or not). space, semicolon and esnext are XO option. They should go directly under the xo config object or under each override.

@devtanc I just tried what you reported on a sample project and it works as expected with the configuration from the doc. The overrides are applied in the the order in which they are defined (so if a file is matched by multiple overrides, the config used is a merge of the matches).

[devtanc]

Oh I see. Yeah, the esnext and the space were just what was in the docs. Thanks for the clarification.