Fix broken Google API URLs #123
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
felixarntz
added
the
[Type] Bug
|
The following accounts have interacted with this PR and/or linked issues. I will continue to update these lists as activity occurs. You can also manually ask me to refresh this list by adding the If you're merging code through a pull request on GitHub, copy and paste the following into the bottom of the merge commit message. To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook. |
JasonTheAdams
approved these changes
Nov 17, 2025
Member
JasonTheAdams
left a comment
JasonTheAdams
left a comment
There was a problem hiding this comment.
Oops! Good catch! LGTM! 🚀
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Yikes! Requests to the Google API are currently not working at all.
Looks like this broke in #115 - more specifically, see https://github.com/WordPress/php-ai-client/pull/115/files#diff-34150b8509051ad1c9d1e475df24d5454c3a994273831cb477bd01fa172b186aR25 🤦
We need more comprehensive testing of the concrete provider implementations to prevent such errors to go unnoticed in the future. I think ideally we can actually fire a cheap request to each provider, to really ensure things work end to end, as this would further help to recognize breakage in case a provider makes a breaking change.