Add typescript typing for components

[JamesPHoughton]

As a developer, I want to use all the code improvement and robustness tools at my disposal so that my code has fewer bugs and is easier to maintain.

TS rules are currently throwing a fit because we don't specify types for components. Should we use typescript or not?

Pros:

• fewer bugs long term
• enforce better coding practices
• better completions and hover prompting in vs code (speed up development)
• learning typescript will be an asset for future job searches for RAs
• types help document what the functions are doing, may make it easier for a new person to learn the code

Cons:

• more work
• we all need to learn how typescript works (and future RAs will too)
• the code is a bit harder to read because

Based on this, and the fact that we have ai tools to help us learn to add types, we decided to commit to typescript more broadly in the project.

First steps:

• [ ] add types wherever vs code complains about not having them
• [ ] when it is easy, but it detailed types (string, number, etc)
• [ ] where we use more complex objects, temporarily use type 'any'

We will try and reuse types created in the validators for some of the more complex objects. This is a separate piece of work tracked here: https://github.com/Watts-Lab/researcher-portal/issues/44

[evanping]

46