feat: update to respect Gradio <= 5.49.0

[Col0ring]

closes #91

[changeset-bot]

🦋 Changeset detected

Latest commit: 4b59af9

The changes in this PR will be included in the next version bump.

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[gemini-code-assist]

Summary of Changes

Hello @Col0ring, 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 focuses on enhancing the project's robustness and forward compatibility with the Gradio library. It introduces specific logic to handle variations in Gradio's API and component initialization across different versions, ensuring that custom components continue to function correctly. The changes primarily involve adapting to Gradio's api_info method and the introduction of the preserved_by_key parameter in BlockContext.

Highlights

• Gradio Version Compatibility: Updated the project to ensure compatibility with Gradio versions up to 5.49.0, addressing potential breaking changes in newer Gradio releases.
• API Information Handling: Introduced an override for the api_info method in ModelScopeComponent to conditionally cache API information based on the installed Gradio version, specifically for versions older than 5.49.0.
• Dynamic Parameter Handling: Implemented dynamic checking for the preserved_by_key parameter in BlockContext initialization, allowing ModelScopeDataLayoutComponent to adapt to different Gradio __init__ signatures.
• Component Inheritance: Refactored ModelScopeDataLayoutComponent to inherit from ModelScopeComponent, aligning its behavior with other custom components.

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 changes to ensure compatibility with different versions of Gradio, specifically handling versions older than 5.49.0. This is achieved by conditionally implementing caching for the api_info method and dynamically adjusting parameters for BlockContext.__init__ using introspection. The PR also refactors component classes by adjusting the inheritance hierarchy, which improves code structure and reduces duplication. The changes are solid, but I have one suggestion to remove a redundant property for better maintainability.

[gemini-code-assist]

This skip_api property is redundant because the parent class ModelScopeComponent already defines it with the same value (False). You can remove this override to simplify the code and rely on the inherited implementation.