Chore/lint type cleanup main - #781
Conversation
|
@DhineshPonnarasan is attempting to deploy a commit to the shashankss1205's projects Team on Vercel. A member of the Team first needs to authorize it. |
…anylinux build step
…ras for PyInstaller build
…for PyInstaller build
… and falkordblite only
…sion checks in PyInstaller spec
d60dbfd to
d01cb48
Compare
…e_sitter_c_sharp/kuzu before build
…B tests with importorskip
…=5.13 install failure
|
👋 Thanks for contributing to CodeGraphContext! Since this PR was opened, |
|
Thanks for the lint/type cleanup effort. Unfortunately this is the kind of PR that conflicts badly with time: it touches 25 files with broad mechanical changes, and against current Rebasing a cleanup PR of this shape is usually more work than redoing it, because the underlying code has changed and the original fixes may no longer apply where they did. If you're still interested, the most effective approach would be to run the linter against current Worth knowing: there are meta-tests that enforce some of this automatically now — Happy to review focused follow-ups. If you'd prefer to drop this one, just let me know and I'll close it. |
Summary
This PR performs a comprehensive cleanup of the codebase to ensure a 100% error-free lint, type-check, and build process.
What was fixed and implemented
TypeScript & ESLint Errors
anyusages, missing/incorrect types, and interface/type issues@typescript-eslint/no-empty-object-typeLocalUploader.tsx,parser.worker.ts, and API handlers)Regex & Validation
Component & API Refactoring
(Note: warnings remain, but no errors)
Dependency Management
Build & Lint Verification
npm run lintandnpm run buildto confirm zero errorsTesting
Remaining Warnings
(e.g., exporting constants/functions alongside components)
Motivation
Closes #770
Hi @Shashankss1205 ,
Please review these changes and let me know if any further modifications are needed. If you notice any issues, please leave a comment below and I’ll address them. Thank you!