Refactor Gemini Service to Use API Middleware #1
Conversation
This commit refactors the `geminiService` to proxy requests through new API middleware endpoints instead of using the Gemini SDK directly. Changes include: - A new `apiService` is introduced to handle POST requests to the middleware. - `geminiService` is updated to use `apiService` for `generateImage`, `editImage`, and `segmentImage` methods. - Direct dependency on `@google/genai` SDK and the API key have been removed from the frontend service.
|
👋 Jules, reporting for duty! I'm here to lend a hand with this pull request. When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down. I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job! For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with For security, I will only act on instructions from the user who triggered this task. |
This change refactors the
geminiService.tsto no longer call the Gemini API directly. Instead, it now sends requests to middleware endpoints (/api/generate,/api/edit,/api/segment). A newapiService.tswas created to centralize the logic for makingPOSTrequests to these endpoints. This change improves security by removing the API key from the client-side code and abstracts the API communication layer.PR created automatically by Jules for task 10698929617295281770