Remove syntax option

docs/user-guide/usage/cli.md

@@ -100,10 +100,6 @@ A filename to assign the input. More info about this option in [standard options
 
 Accept stdin input even if it is empty.
 
-### `--syntax, -s`
-
-Specify a syntax. More info about this option in [standard options](options.md#syntax).
-
 ### `--version, -v`
 
 Show the currently installed version of stylelint.

docs/user-guide/usage/options.md

@@ -87,36 +87,17 @@ If the number of warnings exceeds this value, the:
 - CLI process exits with code `2`
 - Node.js API adds a [`maxWarningsExceeded`](node-api.md#maxwarningsexceeded) property to the returned data
 
-## `syntax`
-
-CLI flags: `--syntax, -s`
-
-Specify a syntax. Options:
-
-- `css`
-- `css-in-js`
-- `html`
-- `less`
-- `markdown`
-- `sass`
-- `scss`
-- `sugarss`
-
-If you do not specify a syntax, stylelint will automatically infer the syntaxes.
-
-Only use this option if you want to force a specific syntax.
-
 ## `customSyntax`
 
 CLI flag: `--custom-syntax`
 
-Specify a custom syntax to use on your code. Use this option if you want to force a specific syntax that's not already built into stylelint.
+Specify a custom syntax to use on your code.
 
 This option should be a string that resolves to a JS module that exports a [PostCSS-compatible syntax](https://github.com/postcss/postcss#syntaxes). The string can be a module name (like `my-module`) or a path to a JS file (like `path/to/my-module.js`).
 
 Using the Node.js API, the `customSyntax` option can also accept a [Syntax object](https://github.com/postcss/postcss/blob/abfaa7122a0f480bc5be0905df3c24a6a51a82d9/lib/postcss.d.ts#L223-L232). Stylelint treats the `parse` property as a required value.
 
-Note that stylelint can provide no guarantee that core rules work with syntaxes other than the defaults listed for the `syntax` option above.
+Note that stylelint can provide no guarantee that core rules work with syntaxes.
 
 ## `disableDefaultIgnores`
 

docs/user-guide/usage/postcss-plugin.md

@@ -6,7 +6,7 @@ _However, if a dedicated stylelint task runner plugin [is available](../integrat
 
 ## Options
 
-The PostCSS plugin uses the [standard options](options.md), _except the `syntax` and `customSyntax` options_. Instead, the syntax must be set within the [PostCSS options](https://github.com/postcss/postcss#options) as there can only be one parser/syntax in a pipeline.
+The PostCSS plugin uses the [standard options](options.md), _except the `customSyntax` option_. Instead, the syntax must be set within the [PostCSS options](https://github.com/postcss/postcss#options) as there can only be one parser/syntax in a pipeline.
 
 ## Usage examples
 

lib/__tests__/__snapshots__/cli.test.js.snap

@@ -47,13 +47,6 @@ exports[`CLI --help 1`] = `
 
       Pattern of files to ignore (in addition to those in .stylelintignore)
 
-    --syntax, -s
-
-      Specify a syntax. Options: \\"css\\", \\"css-in-js\\", \\"html\\", \\"less\\",
-      \\"markdown\\", \\"sass\\", \\"scss\\", \\"sugarss\\". If you do not specify a syntax,
-      syntaxes will be automatically inferred by the file extensions
-      and file content.
-
     --fix
 
       Automatically fix violations of certain rules.

lib/__tests__/standalone-fix.test.js

@@ -25,23 +25,6 @@ it('outputs fixed code when input is code string', async () => {
 	expect(result.output).toBe('a { color: red; }');
 });
 
-it('does not modify shorthand object syntax when autofixing', async () => {
-	const codeString = `const width = '100px'; const x = <div style={{width}}>Hi</div>`;
-
-	const result = await standalone({
-		code: codeString,
-		syntax: 'css-in-js',
-		config: {
-			rules: {
-				indentation: 2,
-			},
-		},
-		fix: true,
-	});
-
-	expect(result.output).toBe(codeString);
-});
-
 it('apply indentation autofix at last', async () => {
 	const result = await standalone({
 		code: