Fix ISSUE: Close TS lint gap: either lint TypeScript or remove it #158#413
Open
ByGamer01 wants to merge 1 commit intocovibes:mainfrom
Open
Conversation
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
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.
Summary
Fix issue TS eslint
Related Issues
There are .ts tests in tests/, but ESLint is not configured to lint TypeScript (no @typescript-eslint/* parser/plugin, and eslint . doesn’t include .ts by default).
Result: TS files can contain “lint disables” that do nothing (e.g. tests/live-streaming-jsonschema.test.ts:2), and TS code gets no pattern enforcement.
Fixes #
Full TS linting:
Changes Made
Update eslint.config.mjs with TS files block using @typescript-eslint/parser and @typescript-eslint/eslint-plugin ; but only for tests/*.ts .
Testing
How was this tested?
with 'npm run list'
Checklist
npm test)