Starting conversion to TypeScript #391
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
longzheng
changed the title
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
I think converting this project to TypeScript will help make it easier to identify and fix type-related bugs and hopefully also make it easier for people to contribute new/changed functionality with more confidence.
I've started laying out the foundations to progressively migrate this project to TypeScript. I plan on converting each of the existing
.jsfiles to.ts.I'm testing along the way with my existing Homebridge installation to make sure I don't break the core functionality, but since I don't have a lot of accessories I can only test the few that I have.
There's a lot about this codebase I'm not familiar with so would appreciate any and all assistance.