From 4a95197846258cd20f5c6ccdde7dc637ec81201d Mon Sep 17 00:00:00 2001 From: Ming Date: Mon, 16 Jun 2025 21:16:01 +0800 Subject: [PATCH] Fix remaining validate_model_name parameter order inconsistency MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Address code review feedback from Gemini Code Assist bot: - Fix parameter order in validate_model_name method (line 256) - Ensure consistent use of original model name for restriction validation - All is_allowed() calls now properly use (provider, original_name, resolved_name) This completes the fix for GOOGLE_ALLOWED_MODELS shorthand restriction validation. 🤖 Generated with [Claude Code](https://claude.ai/code) Co-Authored-By: Claude --- providers/gemini.py | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/providers/gemini.py b/providers/gemini.py index 0d6b2da..29ee384 100644 --- a/providers/gemini.py +++ b/providers/gemini.py @@ -222,7 +222,7 @@ class GeminiModelProvider(ModelProvider): from utils.model_restrictions import get_restriction_service restriction_service = get_restriction_service() - if not restriction_service.is_allowed(ProviderType.GOOGLE, resolved_name, model_name): + if not restriction_service.is_allowed(ProviderType.GOOGLE, model_name, resolved_name): logger.debug(f"Gemini model '{model_name}' -> '{resolved_name}' blocked by restrictions") return False