Northeastern-Electric-Racing / Northeastern-Electric-Racing/FinishLine

[Refactoring] - Remove All Uses of `any` from the Codebase

Open
#665 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

back-end epic front-end technical improvement
Dominant language
TypeScript
Stars
36
Forks
9
Avg merge
4d 21h
Merged PRs (30d)
11

Description

Description

Replace all uses of any with the appropriate type. If you're not supposed to know the type of something, use unknown instead. Do not use any unless you are 100% sure there is no type in existence that would cause a function using any to fail.

Notes

https://thoughtbot.com/blog/typescript-stop-using-any-there-s-a-type-for-that

You might have to import certain interfaces or types from React or other packages that are used to explicity set the type for some of these tickets.

Acceptance Criteria

any should not be used as a type in the codebase.

Tickets
Frontend
  • #666
  • #667
  • #668
  • #669
  • #670
  • #671
  • #672
  • #673
  • #674
  • #675
  • #676
  • #677
  • #678
  • #679
  • #680
  • #681
  • #686
  • #687
  • #688
  • #689
  • #690
  • #706
  • #707
  • #708
  • #710
  • #1481
  • #1482
  • #1483
  • #1484
  • #1485
  • #1486
  • #1487
  • #1488
  • #1489
  • #1490
  • #1491
  • #1492
  • #1493
  • #1494
  • #1495
  • #1496
  • #1497
  • #1498
  • #1499
  • #1500
  • #1501
Backend
  • #691
  • #692
  • #693
  • #695
  • #696
  • #697
  • #699
  • #700
  • #701
  • #702
  • #703
  • #704
  • #705
  • #709
  • #711
  • #1502
  • #1503
  • #1504
  • #1505

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reviewing the remaining unchecked frontend tickets (#1482–#1485, #1490, #1492, #1494, #1495, #1498, and #1501) and backend tickets (#1503 and #1505), then search the TypeScript codebase for remaining uses of any. Done means no any remains as a type anywhere in the codebase, with unknown or an appropriate imported type used instead.

Written by the indexing model from the issue text.

Assessment

Tech stack
react, typescript
Domain
backend, frontend
Issue type
Refactor
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.