Improve TypeScript Type Safety in Utility Function cn

[sarv-tech]

Problem Description

The cn utility function in src/utils/cn.ts is likely used for conditional class name concatenation. However, its current implementation may lack strict TypeScript type safety, which can lead to runtime errors or incorrect class name generation. For example, it might not handle invalid inputs (e.g., null, undefined, or non-string values) gracefully or enforce stricter type constraints.

Current Behavior

The cn function may accept any input without strict type checking, potentially leading to:

• Incorrect class name concatenation.
• Runtime errors when invalid inputs are passed.
• Reduced developer confidence due to lack of type safety.

Expected Behavior

The cn function should:

• Enforce stricter TypeScript types to ensure only valid inputs (e.g., string, undefined, null, or false) are allowed.
• Provide better developer experience with clear type definitions and IntelliSense support.
• Handle invalid inputs gracefully without runtime errors.

Files/Modules Likely Affected

• src/utils/cn.ts

Difficulty Level

Intermediate

Why This Improvement is Valuable

• Enhances the robustness of the utility function, reducing the likelihood of runtime errors.
• Improves developer experience by leveraging TypeScript's type system.
• Aligns with best practices for open-source projects, ensuring high code quality and maintainability.

Acceptance Criteria

• The cn function has updated TypeScript type definitions that enforce stricter input validation.
• Unit tests are added or updated to cover edge cases (null, undefined, false, numbers, etc.).
• The function gracefully handles invalid inputs without throwing runtime errors.
• Documentation is updated to reflect the improved type safety and usage examples.

Labels

• enhancement
• TypeScript
• testing
• good first issue

[sarv-tech]

/assign