ically fixes problems reported by this rule._ Require type imports to be inline. <details><summary>📖 Examples</summary> The following patterns are considered problems: ```js // Options: [{"message":"Type imports should be inline"}] import type { Foo } from './foo'; // Message: undefined // Options: [{"message":"Type imports should be inline"}] import type { Foo } from './foo'; // Message: undefined ``` The following patterns are not considered problems: ```js import { type Foo } from './foo'; import type { Foo } from './foo'; // Options: [{"message":"Type imports should be inline"}] ``` </details> <a name="user-content-eslint-plugin-canonical-rules-prefer-type-import"></a> <a name="eslint-plugin-canonical-rules-prefer-type-import"></a> ### <code>prefer-type-import</code> _The `--fix` option on the command line automatically fixes problems reported by this rule._ Prefer type imports. <details><summary>📖 Examples</summary> The following patterns are considered problems: ```js import { Foo } from './foo'; // Message: undefined import { Foo, Bar } from './foo'; // Message: undefined import { Foo, Bar } from './foo'; // Message: undefined ```