strenghten the eslint rules #60
Open
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.
Remove to exception rules and enforce better type check
Note
Strengthens ESLint TypeScript rules and replaces any with precise/unknown types across extraction, server, logging, and views, adding explicit interfaces and return types.
@typescript-eslint/explicit-function-return-typeand disallow@typescript-eslint/no-explicit-any(tests exempt).anywith concrete/safer types (unknown,Record<string, unknown>, specific interfaces) acrosssrc/.UserInfo,UserApiResponse,ExtendedTransport) and strict return types for handlers.src/extract-tools.ts):x-mcpaccess, and schema mapping (typed properties/items, JSONSchema handling).src/index.ts):transportswithExtendedTransport; annotate MCP handlers (Promise<void>), request parsing, and tool execution result asunknown.src/logger.ts: typedpayload/responseand tool index signature.logs.ts,tool-details.ts): add return types, type payload/response, safer schema formatting.Written by Cursor Bugbot for commit f62fe8a. This will update automatically on new commits. Configure here.