Ambiguous linting on import type and jsdoc
I want to enforce the usage of
import type when no value is referenced in the module, and it works most of the time.
The issue happens when I reference another type using @see in jsdoc, this is very common for foreign keys in DAO / Entity interfaces such as Drizzle / Kysely.
When this kind of reference exists, import type results in errors inside the jsdoc for value referencing; while normal imports results in the lint error of verbatim-module-syntax itself.
How should I make it work?0 Replies