Recently I started noticing models introducing aliases that only rename another type:
type SearchResultType = "deck" | "folder" | "card";
type SearchTab = SearchResultType;
This makes sense because models often optimize for the smallest change, avoiding edits across multiple files that would properly consolidate the types. Yet direct aliases can still be useful for public API compatibility or intentional domain terminology. Derived aliases should also remain valid:
type NestedValue = Source["nested"]["value"];
type Selected = Pick<Source, "id">;
It was relatively easy to prompt AI to create slop-scan plugin to catch such issues.
Thoughts on including it in the core repo? Thank you
Recently I started noticing models introducing aliases that only rename another type:
This makes sense because models often optimize for the smallest change, avoiding edits across multiple files that would properly consolidate the types. Yet direct aliases can still be useful for public API compatibility or intentional domain terminology. Derived aliases should also remain valid:
It was relatively easy to prompt AI to create
slop-scanplugin to catch such issues.Thoughts on including it in the core repo? Thank you