chore: strengthen typescript safety and enable strict mode - #34
Merged
Conversation
Collaborator
Author
|
These changes strictly remove any and improve type safety without modifying any logic. All tests and CI checks pass cleanly, so I'm merging this now. |
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Tightens type safety across the project without altering any algorithms.
Strict Mode: Enabled "strict": true in tsconfig.json and added npm run typecheck to CI.
Removed any: Added explicit types for Joplin API responses, worker variables, and experimental joplin.ai calls.
Safe Error Handling: Converted catch (err: any) blocks to type-safe unknown error handling.
Verification: All 137 unit tests, linter checks, typechecks, and build steps (npm run ci) pass cleanly.