chore: add type-check to pre-commit

[lyzno1]

Important

1. Make sure you have read our contribution guidelines
2. Ensure there is an associated issue and you have been assigned to it
3. Use the correct syntax to link this PR: Fixes #<issue number>.

Summary

Screenshots

Before	After
...	...

Checklist

• This change requires a documentation update, included: Dify Document
• I understand that this PR may be closed in case there was no previous discussion or issues. (This doesn't apply to typos!)
• I've added a test for each change that was introduced, and I tried as much as possible to make a single atomic change.
• I've updated the documentation accordingly.
• I ran dev/reformat(backend) and cd web && npx lint-staged(frontend) to appease the lint gods

[gemini-code-assist]

Summary of Changes

Hello @lyzno1, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request enhances the development workflow by adding a TypeScript type-checking step to the pre-commit hook for the web directory. This change ensures that all code committed to the repository adheres to strict type safety, thereby improving overall code quality and reducing the likelihood of introducing type-related errors into the main branch.

Highlights

• Pre-commit Hook Enhancement: Integrated TypeScript type-checking into the web directory's pre-commit hook, ensuring that all staged changes are type-checked before a commit is allowed.
• Code Quality Enforcement: The pre-commit process will now fail and prevent a commit if any TypeScript type errors are detected, promoting higher code quality and preventing type-related bugs from entering the codebase.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

This pull request adds a TypeScript type-checking step to the pre-commit hook for the web frontend. This is a great addition for maintaining code quality. My review includes a suggestion to optimize this new step by only running it when TypeScript files have actually been modified, which will improve the pre-commit hook's performance.

[lyzno1]

/gemini review

[gemini-code-assist]

Code Review

This pull request adds a TypeScript type-checking step to the pre-commit hook, which is a great improvement for code quality. The check is smartly conditioned to run only when TypeScript files are staged, which is efficient. My review includes a minor suggestion to make the shell script logic more concise and idiomatic.

[lyzno1]

/gemini review

[gemini-code-assist]

Code Review

This pull request adds a TypeScript type-checking step to the pre-commit hook. The implementation correctly checks for staged TypeScript files before running the type check. My feedback includes a suggestion to refactor a portion of the shell script to improve readability and maintainability by using a case statement, which is a more idiomatic way to handle different exit codes from the git diff command.