feat: to support tool multi-select input

[hjlarry]

Pull Request Checklist

to support langgenius/dify#29180

depends on: langgenius/dify-plugin-daemon#523

Thank you for your contribution! Before submitting your PR, please make sure you have completed the following checks:

Compatibility Check

• I have checked whether this change affects the backward compatibility of the plugin declared in README.md
• I have checked whether this change affects the forward compatibility of the plugin declared in README.md
• If this change introduces a breaking change, I have discussed it with the project maintainer and specified the release version in the README.md
• I have described the compatibility impact and the corresponding version number in the PR description
• I have checked whether the plugin version is updated in the README.md

Available Checks

• Code has passed local tests
• Relevant documentation has been updated (if necessary)

[gemini-code-assist]

Summary of Changes

Hello @hjlarry, 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 introduces the capability for tool parameters to handle multi-select inputs. This enhancement allows for greater flexibility in defining tool behaviors, particularly for parameters that require users to choose multiple options from a predefined or dynamically generated list. The changes primarily involve updating the ToolParameter data model to accommodate this new functionality.

Highlights

• Enhanced Tool Parameter Flexibility: The default field within the ToolParameter class has been updated to support lists, allowing for default values that are collections of items.
• Multi-Select Input Support: A new boolean field, multiple, has been introduced to the ToolParameter class. This field, specifically for select or dynamic-select parameter types, indicates whether the parameter can accept multiple selections.

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 introduces support for multi-select inputs in tools by modifying the ToolParameter entity. It correctly updates the default field to allow list values and adds a new multiple boolean flag. The implementation is straightforward. My review includes a suggestion to add validation logic to the ToolParameter model to ensure data consistency and prevent invalid configurations, which would improve the overall robustness of the implementation.