Is your feature request related to a problem? Please describe.
Despite the Svelte project being configured for TypeScript, with many components flagged using lang=ts, the utilization of types throughout the codebase is inconsistent. This leads to challenges in maintaining the code and results in numerous errors flagged by the language server, complicating development.
Describe the solution you'd like
To improve code quality and developer experience, I propose refactoring the existing code to ensure appropriate usage of TypeScript types wherever feasible. Additionally, incorporating type declarations for external libraries within package.json will enhance compatibility and reduce language server errors.
Additional context
I plan to use this project at my company and am ready to dedicate time to enhance it. If this aligns with the project's goals, I'm eager to help implement these improvements.
Originally created by @Carlos-err406 on GitHub (Feb 27, 2024).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/944
**Is your feature request related to a problem? Please describe.**
Despite the Svelte project being configured for TypeScript, with many components flagged using lang=ts, the utilization of types throughout the codebase is inconsistent. This leads to challenges in maintaining the code and results in numerous errors flagged by the language server, complicating development.
**Describe the solution you'd like**
To improve code quality and developer experience, I propose refactoring the existing code to ensure appropriate usage of TypeScript types wherever feasible. Additionally, incorporating type declarations for external libraries within package.json will enhance compatibility and reduce language server errors.
**Additional context**
I plan to use this project at my company and am ready to dedicate time to enhance it. If this aligns with the project's goals, I'm eager to help implement these improvements.
Feel free to make a PR! Just a warning this project is still being actively developed and a lot of the code will be either replaced in favour of other implementations or removed entirely, so it's probably best if you focus on only the core part of the code. Good luck!
<!-- gh-comment-id:1967684363 -->
@tjbck commented on GitHub (Feb 27, 2024):
Feel free to make a PR! Just a warning this project is still being actively developed and a lot of the code will be either replaced in favour of other implementations or removed entirely, so it's probably best if you focus on only the core part of the code. Good luck!
@Carlos-err406 commented on GitHub (Feb 28, 2024):
Thanks for the heads up! I'll be extra careful to make the changes without causing hiccups in the main development.
<!-- gh-comment-id:1969153101 -->
@Carlos-err406 commented on GitHub (Feb 28, 2024):
Thanks for the heads up! I'll be extra careful to make the changes without causing hiccups in the main development.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Originally created by @Carlos-err406 on GitHub (Feb 27, 2024).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/944
Is your feature request related to a problem? Please describe.
Despite the Svelte project being configured for TypeScript, with many components flagged using lang=ts, the utilization of types throughout the codebase is inconsistent. This leads to challenges in maintaining the code and results in numerous errors flagged by the language server, complicating development.
Describe the solution you'd like
To improve code quality and developer experience, I propose refactoring the existing code to ensure appropriate usage of TypeScript types wherever feasible. Additionally, incorporating type declarations for external libraries within package.json will enhance compatibility and reduce language server errors.
Additional context
I plan to use this project at my company and am ready to dedicate time to enhance it. If this aligns with the project's goals, I'm eager to help implement these improvements.
@tjbck commented on GitHub (Feb 27, 2024):
Feel free to make a PR! Just a warning this project is still being actively developed and a lot of the code will be either replaced in favour of other implementations or removed entirely, so it's probably best if you focus on only the core part of the code. Good luck!
@Carlos-err406 commented on GitHub (Feb 28, 2024):
Thanks for the heads up! I'll be extra careful to make the changes without causing hiccups in the main development.