Feat#16: changed routes.py to facilitate support of character cards.

[NBD-1138]

#16

Helps add a button in UI to select Live2d model when importing Sillytavern character card.
Endpoint for upload of card, generation of character\NAME.yaml. from card.

Corresponding changes to frontend: Open-LLM-VTuber/Open-LLM-VTuber-Web#16

[gemini-code-assist]

Summary of Changes

Hello @NBD-1138, 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 expands the backend capabilities for managing character data, specifically enhancing support for Live2D models and character cards. It introduces new API endpoints that allow for fetching available Live2D models, uploading character avatars, and creating comprehensive character configuration files. These changes are crucial for enabling a more dynamic and user-friendly experience when importing and configuring characters within the application, directly supporting the UI's ability to select Live2D models when importing Sillytavern character cards.

Highlights

• New API for Live2D Models: Introduced a GET endpoint "/api/live2d/models" to retrieve a list of available Live2D models from "model_dict.json", facilitating model selection in the UI.
• Avatar Upload Functionality: Added a POST endpoint "/api/avatars/upload" that allows users to upload PNG avatar images. This includes robust handling for filename sanitization, uniqueness, and error management.
• Character Configuration Creation: Implemented a POST endpoint "/api/characters/create" to generate new character YAML configuration files. This endpoint validates input, ensures unique character names and UIDs, and integrates with Live2D model selection and avatar uploads.
• Enhanced Utility Functions: A suite of new helper functions ("_sanitize_name", "_ensure_unique_basename", "_load_model_dict", "_collect_existing_conf_uids", "_generate_conf_uid", "_validate_model_name") were added to support robust file and name management for characters and models.

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 new API endpoints and helper functions to support the creation of character cards, which is a great addition. The code is generally well-structured. My review focuses on improving adherence to the project's style guide, particularly regarding type hints and docstring formatting, and on enhancing maintainability by replacing hardcoded strings with constants. Addressing these points will improve the overall code quality and consistency.