Skip to content

try: check for wp_supports_ai in WP_AI_Client_Prompt_Builder::__call() #2

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
justlevine wants to merge 1 commit into from
Closed

try: check for wp_supports_ai in WP_AI_Client_Prompt_Builder::__call() #2

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
13 changes: 8 additions & 5 deletions src/wp-includes/ai-client/class-wp-ai-client-prompt-builder.php
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -178,11 +178,6 @@ class WP_AI_Client_Prompt_Builder {
*/
public function __construct( ProviderRegistry $registry, $prompt = null ) {
try {
if ( ! wp_supports_ai() ) {
// The catch block will convert this to a WP_Error.
throw new \RuntimeException( __( 'AI features are not supported in this environment.' ) );
}

$this->builder = new PromptBuilder( $registry, $prompt );
} catch ( Exception $e ) {
$this->builder = new PromptBuilder( $registry );
Expand Down Expand Up @@ -281,6 +276,14 @@ public function using_abilities( ...$abilities ): self {
* @return mixed The result of the method call.
*/
public function __call( string $name, array $arguments ) {
// Check whether AI is supported before proceeding with any method call.
if ( null === $this->error && ! wp_supports_ai() ) {
Copy link
Copy Markdown
Owner Author

@justlevine justlevine Mar 12, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The downside to this approach is that this check runs on every single successful call. We could mitigate it by adding a state property to the class, something which isn't necessary when the ::$error is set in the constructor.

$this->error = new WP_Error(
'ai_not_supported',
__( 'AI features are not supported in this environment.' )
);
}

/*
* If an error occurred in a previous method call, either return the error for terminate methods,
* or return the same instance for other methods to maintain the fluent interface.
Expand Down
Loading