[Task](exampleapp): Migrate Example App to TypeScript Using ts-migrate tool

[edda]

Description

Migrate the example application from JavaScript to TypeScript using the airbnb ts-migrate tool. Document any insights on the tool's effectiveness, including challenges, limitations, and helpful tips for usage.

Acceptance Criteria

• Migrate the codebase of the example app from JavaScript to TypeScript.
• Use ts-migrate as the primary tool for the migration.
• Document findings on:
  • Benefits and shortcomings of ts-migrate
  • Usability tips and best practices for others performing similar migrations
• Add any additional observations that may assist with future migrations.

Notes

• Include your documentation in our team docu
• Consider any edge cases or manual adjustments needed during the migration process.

Resources

• ts-migrate GitHub repository

[guoda-puidokaite]

Update (13th Jan, 2025)

• Example app has been migrated from JavaScript to TypeScript with PR (chore(ui): migrate example app to ts #696).
• Type issues have been silenced for now, until ui-components are revisited (in tickets below).
• ts-migrate tool:
  • Was mostly helpful to rename files automatically and change components to Typescript signature.
    • Note: Since the tool automatically migrated all files, we need to make sure to keep ones in the public folder as js.
  • Only added type any. Correct typing needs to be done by the developer.
  • Introduced many error ignore lines that polluted the code for issues that didn't exist. Our ts configuration wasn't picked up (there's most likely a solution). I removed these and silenced or resolved any type issues that existed manually.

Update (27th Jan, 2025)

• There were many type issues in apps trying to use ui-components. Investigation [Task](ui-components): Typescript children default value removal and also add default value if necessery for other properties #678 is now complete. The ui-components vite configuration has been fixed and types are finally fully supported.
• All example app components have been converted to TS syntax and types added in many files in a 1st iteration PR chore(example): improve example app types (1st iteration) #734. However, further improvements are needed.
• Currently double checking all ui-components types in ticket [Task](context): Double check prop types #664.

Next:

• Will go through the example app and remove unnecessary experimental files.
• Then, will continue migrating example app with this ticket, adding correct types and resolving the remaining silenced issues.