All conformance tests

/conf/overrides/

• /conf/overrides/aliases-existing-rule: An alias an override declares does not change a rule the ruleset defines: the rule keeps the ruleset's alias and only its severity changes.
• /conf/overrides/aliases-new-rule: A rule an override defines resolves aliases against the override's, which take precedence over the ruleset's alias of the same name.
• /conf/overrides/aliases-outside-globs: Outside the override's globs its aliases have no effect, and the rule keeps its default severity.
• /conf/overrides/extends: An override's extends adds rules for the documents it matches.
• /conf/overrides/extends-with-rules: An applying override with extends and rules adds to the rulesets the ruleset extends: a, b, and r all run.
• /conf/overrides/extends-without-rules: An applying override with extends and no rules replaces the rulesets the ruleset extends: b and the ruleset's own r run, a does not.
• /conf/overrides/file-scoped-empty: A file-scoped override with neither extends nor rules is invalid.
• /conf/overrides/file-scoped-valid: A file-scoped override with rules, extends, formats, parserOptions, and aliases is valid.
• /conf/overrides/mixed-globs: An override whose files mix a pointer glob and a plain glob is file-scoped, so it can define rules with shorthands and is valid.
• /conf/overrides/order: Of two overrides that both match, the later one wins.
• /conf/overrides/pointer-scope: A pointer-scoped override silences the rule under its pointer only.
• /conf/overrides/pointer-scope-at: A pointer that names the result's own location silences it.
• /conf/overrides/pointer-scoped-extends: A pointer-scoped override with extends is invalid.
• /conf/overrides/pointer-scoped-rule-object: A pointer-scoped override that defines a rule object is invalid.
• /conf/overrides/pointer-scoped-valid: A pointer-scoped override whose rules are severities only is valid.
• /conf/overrides/redefined-rule-alias-applied: An override that redefines a rule with an alias only the override declares makes a linter reject the ruleset for a document it applies to.
• /conf/overrides/redefined-rule-alias-declared: An override that redefines a rule with an alias the ruleset declares is loaded, and the redefined rule runs.
• /conf/overrides/scope-match: A document inside the override's globs gets the override's severity.
• /conf/overrides/scope-no-match: A document outside the override's globs keeps the base severity.
• /conf/overrides/scope-outside-ruleset-directory: The same glob does not match a document in a legacy/ directory that is not next to the ruleset, whatever the working directory.
• /conf/overrides/scope-ruleset-directory: A glob is matched against the document's path relative to the ruleset file's directory, so legacy/** matches a document in legacy/ next to the ruleset.
• /conf/overrides/shape-empty: An empty overrides array is invalid.
• /conf/overrides/shape-no-files: An override without files is invalid.
• /conf/overrides/shape-valid: An override with a non-empty files array is valid.
• /conf/overrides/unknown-property-applied: An override with a property the Ruleset Object does not have makes a linter reject the ruleset for a document it applies to.
• /conf/overrides/unknown-property-not-applied: The same override, applying to no document being linted, does not stop the ruleset from loading.