Correct use of typescript type declarations in the codebase

[rigolepe]

Feature Request

The generation of typescript type declarations fails: npx tsc. The errors can be revealed by running the existing type-check script for the frontend codebase:

npm run type-check

gives:

Found 27 errors in 18 files.

Errors  Files
     1  src/components/common/animatedNumbers/index.tsx:2
     1  src/components/common/arrayReaderComponent/index.tsx:1
     1  src/components/core/parameterRenderComponent/components/tableComponent/components/loadingOverlay/index.tsx:1
     1  src/CustomNodes/NoteNode/components/color-picker-buttons.tsx:3
     1  src/icons/AIML/index.tsx:6
     1  src/icons/athena/index.tsx:9
     1  src/icons/freezeAll/index.tsx:9
     1  src/icons/Perplexity/index.tsx:2
     3  src/modals/codeAreaModal/index.tsx:180
     1  src/modals/IOModal/components/chatView/chatInput/hooks/use-handle-file-change.ts:8
     1  src/pages/FlowPage/components/extraSidebarComponent/index.tsx:224
     1  src/pages/FlowPage/components/extraSidebarComponent/SidebarCategoryComponent/index.tsx:2
     1  src/pages/MainPage/oldComponents/componentsComponent/index.tsx:164
     1  src/pages/MainPage/utils/handle-download-folder.ts:2
     3  src/pages/ProfileSettingsPage/index.tsx:9
     1  src/pages/SettingsPage/pages/GeneralPage/components/ProfileGradientForm/index.tsx:2
     1  src/pages/SettingsPage/pages/GlobalVariablesPage/index.tsx:41
     6  src/reportWebVitals.ts:1

The errors above ensure that editors (such as vscode) are littered with "red underlined code" because of incomplete type information. This undercuts the advantage of using typescript in the first place.

Motivation

Typescript enforces type safety, but it looks like this feature is a ignored in a lot of files. A lot can be fixed quickly by correcting the import paths.

Your Contribution

I could prepare a PR if core developers have no time to have a look at this. Let me know.

[TejasQ]

I've created a PR (#6914) that addresses one of the TypeScript issues mentioned in this issue.

The PR converts the AI-ML.jsx file to TypeScript and adds proper type definitions. This should help reduce the TypeScript errors when running npm run type-check.

If you'd like me to address more of the TypeScript issues, please let me know!

[TejasQ]

...Cursor/Claude did all this autonomously with my API key... I'm sorry if this is incorrect.

[dosubot]

Hi, @rigolepe. I'm Dosu, and I'm helping the langflow team manage their backlog. I'm marking this issue as stale.

Issue Summary:

• You reported TypeScript type declaration errors affecting code editors like VSCode.
• @TejasQ responded with a PR (fix: Fix TypeScript issues with AI-ML component #6914) that converts a file to TypeScript and adds type definitions.
• @TejasQ expressed willingness to address more TypeScript issues if needed.

Next Steps:

• Please let us know if this issue is still relevant to the latest version of the langflow repository by commenting here.
• If no further input is provided, the issue will be automatically closed in 7 days.

Thank you for your understanding and contribution!