fix(aihubmix_image): fix reference image form type from llm to form

[xinrui-z]

Related Issues or Context

This PR contains Changes to Non-Plugin

• Documentation
• Other

This PR contains Changes to Non-LLM Models Plugin

• I have Run Comprehensive Tests Relevant to My Changes

This PR contains Changes to LLM Models Plugin

• My Changes Affect Message Flow Handling (System Messages and User→Assistant Turn-Taking)

• My Changes Affect Tool Interaction Flow (Multi-Round Usage and Output Handling, for both Agent App and Agent Node)

• My Changes Affect Multimodal Input Handling (Images, PDFs, Audio, Video, etc.)

• My Changes Affect Multimodal Output Generation (Images, Audio, Video, etc.)

• My Changes Affect Structured Output Format (JSON, XML, etc.)

• My Changes Affect Token Consumption Metrics

• My Changes Affect Other LLM Functionalities (Reasoning Process, Grounding, Prompt Caching, etc.)

• Other Changes (Add New Models, Fix Model Parameters etc.)

Version Control (Any Changes to the Plugin Will Require Bumping the Version)

• I have Bumped Up the Version in Manifest.yaml (Top-Level Version Field, Not in Meta Section)

Dify Plugin SDK Version

• I have Ensured dify_plugin>=0.3.0,<0.6.0 is in requirements.txt (SDK docs)

Environment Verification (If Any Code Changes)

Local Deployment Environment

• Dify Version is: , I have Tested My Changes on Local Deployment Dify with a Clean Environment That Matches the Production Configuration.

SaaS Environment

• I have Tested My Changes on cloud.dify.ai with a Clean Environment That Matches the Production Configuration

[gemini-code-assist]

Summary of Changes

Hello @xinrui-z, 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 addresses a configuration inconsistency in several image processing tools by standardizing the input form type for reference images. The change ensures that image inputs are correctly recognized as 'form' types rather than 'LLM' types, which is crucial for proper integration with Dify's workflow system. Additionally, the descriptions for these image parameters have been enhanced to better communicate their compatibility with workflow variables and node connections, improving user understanding and system interoperability.

Highlights

• Configuration Fix: Corrected the form type for reference/input image parameters in multiple image-related tools (Doubao, ERNIE iRAG Edit, GPT Image Edit, Qwen Image Edit) from llm to form.
• Improved Descriptions: Updated human_description and llm_description for image parameters to explicitly mention support for workflow variable pools and node connections, enhancing clarity for users and LLMs.

🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console.

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 correctly changes the form type for image input parameters from llm to form across several tool definition files. This is a necessary fix to enable image inputs to be properly handled as form fields in the Dify UI, allowing for file uploads and connections from other workflow nodes. The changes are consistent and correct. I've added one comment on gpt-image-edit.yaml to suggest updating the parameter's description for consistency and clarity, similar to how it was done in doubao.yaml. Otherwise, the changes look good.

[gemini-code-assist]

While changing the form type to form is correct, the descriptions for this image parameter should also be updated to reflect the new capabilities, ensuring consistency with other tools. The current human_description and llm_description don't mention support for workflow connections or Dify file variables, which this change enables. Please consider updating them for better user clarity, similar to the changes made in doubao.yaml and other files in this PR.