[v4] refactor model_type template

[Jintao-Huang]

No description provided.

[gemini-code-assist]

Summary of Changes

Hello @Jintao-Huang, 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 significantly refactors the model registration system by enhancing the flexibility of template assignments. It shifts the definition of the template parameter from the broader ModelMeta to individual ModelGroup instances, enabling more precise control over model variants. This change also involves a substantial consolidation of specific model types into more general categories, simplifying the overall model constant definitions and updating all affected model registration calls and documentation accordingly.

Highlights

• Refactored Model Template Definition: The template parameter, previously a required attribute of ModelMeta, has been moved to an optional attribute within ModelGroup. This allows for more granular template specification for different model variants within the same overall model type.
• Consolidation of Model Types: Numerous specific LLMModelType and MLLMModelType entries (e.g., qwen2_5_math, qwq, ernie_thinking, yi_coder) have been removed from swift/llm/model/constant.py. These specific model variants are now handled more flexibly by specifying their template directly within their respective ModelGroup definitions, leading to a cleaner and more streamlined model registration system.
• Updated Model Registration Calls: Across various model definition files, the template argument in register_model calls has been changed from a positional argument to an explicit keyword argument (template=TemplateType.xxx or template='custom'). Additionally, many ModelGroup definitions now directly embed their TemplateType.
• Documentation and Type System Updates: Documentation files have been updated to reflect that the template parameter for ModelMeta is no longer required and defaults to None. Assertions have also been added in ModelGroup and ModelMeta for type checking related to the template and get_function attributes.

🧠 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 introduces a significant and well-executed refactoring of the model registration mechanism. By making the template parameter optional in ModelMeta and introducing it in ModelGroup, you've successfully consolidated numerous model registrations, which greatly simplifies the codebase and improves maintainability. The changes are consistently applied across all relevant files, including documentation. I have a couple of minor suggestions for further cleanup, but overall, this is a great improvement.

[gemini-code-assist]

The model_type qwen2_5 is kept here, but its registration in swift/llm/model/model/qwen.py has been removed. The models previously under this type are now merged into the qwen2 model registration, using qwen2_5 as a template type. To maintain consistency and avoid potential confusion, it would be best to remove qwen2_5 from LLMModelType as it's no longer a registered model type.

[gemini-code-assist]

There's an extra space at the beginning of this line, which makes the indentation inconsistent with the surrounding ModelGroup definitions. Please remove the leading space for consistency.

Suggested change

	ModelGroup([Model('AIDC-AI/Marco-o1', 'AIDC-AI/Marco-o1')], TemplateType.marco_o1),
	ModelGroup([Model('AIDC-AI/Marco-o1', 'AIDC-AI/Marco-o1')], TemplateType.marco_o1),