type-system-governance

To enforce a single TypeScript types directory, configure ESLint rules around a dedicated /types folder and run yarn lint. This prevents inline type definitions by ensuring new interfaces, DTOs, and props are placed in canonical files and consistently imported across your codebase.

The best way to organize TypeScript types is centralizing them in a /types directory. This approach prevents duplicate definitions across components by making /types the canonical source for all interfaces and props, ensuring DRY and predictable import paths throughout your project.

To move inline TypeScript types like ButtonProps into a centralized folder, extract the type definition and place it in a file such as types/props.ts. Then, adjust your components to import these types from the /types directory to maintain import consistency.

Yes, you can use ESLint to enforce code organization rules for TypeScript interfaces and DTOs. By enabling specific ESLint rules around a dedicated /types directory, the linter flags inline type definitions and ensures all new types are placed in canonical files.

You should keep all TypeScript types in a /types directory during code reviews to maintain a clean, scalable codebase. This practice prevents inline type definitions and duplication, ensuring new interfaces and props are consistently imported from canonical files.