Migration to TypeScript with type-safe reasons array #30
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR introduces a full TypeScript upgrade, improving maintainability and scalability by structuring the codebase and data more robustly.
🔧 What’s Changed
🎯 Why It Matters
✅ TypeScript provides a better developer experience with static type checks
✅ Eliminates runtime file I/O in favor of static imports
✅ Structured reasons array prepares the codebase for future features (e.g., filtering, categorization, tagging)
🧪 How to Test
Run the app as usual (npm run dev)
Test endpoint (e.g., /random-reason) still returns a valid JSON object:
{ reason: "..." }
Types validated via tsc with no type errors