- Issue created by @dmundra
- Merge request !11#3539604 Targeting gemini_provider module from an issue fork β (Open) created by dmundra
- πΊπΈUnited States dmundra Eugene, OR
I followed https://jaybeaton.com/blog/how-use-version-module-drupal-issue-fork-comp... to install the issue fork https://git.drupalcode.org/issue/gemini_provider-3519469 code as a package to the composer.json so it can be installed locally for testing.
Adding tests/ai-test-drush-scripts/GeminiFunctionCallTester.php to test function calls.
QA steps:
- Checkout the branch from this issue's MR.
- Run ddev like normal
- Run ddev poser to install different version of the gemini_provider module and the dependencies google-gemini-php/client and drupal/ai_agents
- Configure Gemini AI following contributing steps (if haven't done before)
- Run
ddev drush php-script tests/ai-test-drush-scripts/GeminiFunctionCallTester.php
- Confirm it outpus 140. Change the prompt in the test file and run it again to confirm the calculator function works.
- πΊπΈUnited States majorrobot
Thanks for doing this, @dmundra! What is your thought re: getting Structured Output added? Does this need to be merged before that can be done?
- πΊπΈUnited States dmundra Eugene, OR
I think either add it to β¨ Support tools calling Active or copy the changes from that ticket to β¨ Upgrade to 2.0 version of google-gemini-php Active and then add it there.
- πΊπΈUnited States majorrobot
I'm thinking we might not want to merge this atm -- we will have the update the commit ref in `composer.json` whenever there is a new commit in the MR. I'm thinking we should wait to act until the change is merged in or at least more stable. Thoughts, @dmundra?