ESLint rule and have Prettier handle import type { Type } Pattern

[JacobMGEvans]

    > Is there something wrong with the `import { type ..., ... }` pattern? I think I've used that in various places

@penalosa consistency, we started with the import type { FetchError } from "../cfetch"; and would like to keep it consistent, we should at it as a ESLint rule and have Prettier handle it if it can.

Originally posted by @JacobMGEvans in #2064 (comment)
Cc: @penalosa

[mrkldshv]

Hey! Is this issue free to pick up?

[JacobMGEvans]

Sure 😄

[mrkldshv]

To give an update here: the change that allows to enforce such pattern was just merged. I'll update the configuration in the repository when the release with this PR is published.

[mrkldshv]

It seems like we also need to this rule to be released to be able to enforce import type {} pattern. Will be tracking new releases of eslint-plugin-import.

[JacobMGEvans]

Just following up on this, are you still working on this @mrkldshv ?

[mrkldshv]

Sure! From what I understood we'd need release of https://github.com/import-js/eslint-plugin-import to make it work. The old version doesn't have consistent-type-specifier-style rule. Let me know if we can do anything meanwhile!