chore: [#0] Improve type accuracy, strict mode compatibility and JSDoc documentation #1677
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.
Fixes several easy to fix issues with TypeScript types accuracy, strict mode compatibility and JSDoc documentation.
While in non-strict mode, which you currently use, you will see no difference, you're 10% closer to enabling strict mode now!
Before, in strict mode:
After, in strict mode:
Most common issues:
null
not accepted where some value or undefined was accepted(arg: any) => void | null
does NOT mean the same as((arg: any) => void) | null
- the former means "a function that returns nothing or returns null", the latter - "a function that returns nothing, or no function (null)"