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 did a fresh checkout of Signal just now. To my surprise,
npm run build
followed bynpm start
ended up showing two compile errors. When I opened it in Webstorm the IDE confirmed there were problems.Problem 1
Since
selectedCategoryId
is a number, thenSelectBox<T>
becomesSelectBox<number>
. However,SelectBox
currently requiresSelectBox<T extends object>
, causing an error becausenumber
doesn't extendobject
.Solution 1
Removed
extends object
Problem 2
The above
onMouseDown
method only takes 4 arguments:Solution 2
Removed
eventType,
from the list of args passed toonMouseDown
Looking at the git blame, those lines of code haven't changed in a very long time (since 2022), so I wonder why the compiler is suddenly detecting these errors. Were there recent changes to tsconfig? Or could it be because you made
eslint
changes? Either way, it's nice that these were caught. (Maybe they were warnings before?)