-
-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Maintenance] TypeScript migration #1483
Comments
While looking at this, I found a cool package (https://github.com/codemix/deprank) that uses PageRank algorithm to find the 'most important' files in the project and list out dependencies. This can give a good idea of which files are good to tackle first for JS -> TS conversion (and which files may be more challenging). Here's the command I ran for |
@MatissJanis I think we should pin this so that community is aware that the project is still accepting typescript PRs. |
That makes sense @joel-jeremy , but we can only pin 3x issues. Perhaps lets wait for one of the experimental features to be released and then pin this one? |
browser-server.js to browser-server.ts and updates browser-preload.browser.js
The majority of the codebase has been migrated to TypeScript. Pinning this issue to give it more visibility. If folks want to contribute - working on the TS migration is an easy way to learn more about the Actual codebase while also benefiting the community. |
Updated the root description with a list of files remaining. Not much to go to be 100% TS compliant! |
We are currently at around 50% TypeScript. There is still lots of work to be done to get to 100%.
Feel free to help out by converting a file here and there. Also hardening the existing TS files is welcome (i.e. converting
unknown
andany
to more strict types).Please do not send massive migration PRs. Try to keep it small and isolated.
Remaining files:
RecurringSchedulePicker.jsx
->RecurringSchedulePicker.tsx
#3396The text was updated successfully, but these errors were encountered: