Refactor Typescript and ESLint configuration file. #19
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.
This pull request primarily focuses on cleaning up and modernizing the project's linting and TypeScript configuration.
Linting and ESLint Configuration Updates:
eslint.config.mjsto usedefineConfig, updated toglobals.es2026, removed theeslint-plugin-jestdependency and related rules, simplified file globs, and streamlined import rules for consistency and maintainability.eslint-plugin-jestpackage frompackage.jsonas it is no longer needed.TypeScript Configuration Cleanup:
tsconfig.build.jsonandtsconfig.eslint.json, removing redundant or unused TypeScript project configurations.VSCode Settings Improvements:
.vscode/settings.jsonto always fix ESLint and organize imports on save, removed deprecated or redundant settings, and improved formatting consistency.Temporary TypeScript Strict Mode Workarounds:
@ts-expect-error FIXME: error after turning strict on.comments throughout test and implementation files to suppress type errors after enabling TypeScript strict mode. These are intended as temporary workarounds until proper fixes can be implemented.