Repository navigation
Fix lint warnings - #54
Merged
Merged
Conversation
Replace non-null assertions with optional chaining and explicit null guards so `npm run lint` reports no warnings. - vocabularyDump: iterate Map entries instead of get(tag)! - competence test: explicit null guard before toBeLessThan - gotalkNow tests: optional chaining inside expect(...) - opml roundtrip test: nullish fallback for targetPageId - vocabularyDump test: explicit guard after a null check
Collaborator
|
Thanks Chris — merged. |
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
2 participants
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.
Replace non-null assertions with optional chaining and explicit null guards so
npm run lintreports no warnings.