With @subsquid/typeorm-codegen 2.4.0, every generated entity begins by registering Entity, Column, and PrimaryColumn imports. Column is only needed for enum fields, so models containing no enum fields generate an unused Column as Column_ import.
For example, an entity composed of ID, String, Int, BigInt, and DateTime fields generates Column_ even though the generated class never references it. This creates unused-import findings in static analysis tools such as CodeQL.
Could the generator register Column only in the enum-field branch, alongside the existing decorator-specific imports? That would keep generated models clean without downstream post-processing.
With
@subsquid/typeorm-codegen2.4.0, every generated entity begins by registeringEntity,Column, andPrimaryColumnimports.Columnis only needed for enum fields, so models containing no enum fields generate an unusedColumn as Column_import.For example, an entity composed of
ID,String,Int,BigInt, andDateTimefields generatesColumn_even though the generated class never references it. This creates unused-import findings in static analysis tools such as CodeQL.Could the generator register
Columnonly in the enum-field branch, alongside the existing decorator-specific imports? That would keep generated models clean without downstream post-processing.