Instead of using the GOOGLE_API_KEY by default, we're checking for the GEMINI_API_KEY ones first since its naming is less misleading. The GOOGLE_API_KEY is still kept for consistency.
Motivation
The Google API key can be misleading since it's not really an overall key for all of Google API and only for the Gemini ones.
Type of change
Choose one: Feature request
Checklist
[X] I have performed a self-review of my code.
[X] I have added detailed comments to my code where applicable.
[X] I have verified that my change does not break existing code.
[X] My PR is based on the latest changes of the main branch (if unsure, please run git pull --rebase upstream main).
[X] I am familiar with the Google Style Guide for the language I have coded in.
Description of the change
Instead of using the
GOOGLE_API_KEYby default, we're checking for theGEMINI_API_KEYones first since its naming is less misleading. TheGOOGLE_API_KEYis still kept for consistency.Motivation
The Google API key can be misleading since it's not really an overall key for all of Google API and only for the Gemini ones.
Type of change
Choose one: Feature request
Checklist
git pull --rebase upstream main).