- 
                Notifications
    
You must be signed in to change notification settings  - Fork 34
 
Clarify Documentation for OpenAI-Compatible Base Classes Used by Multiple Providers #95 #97
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.
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
Conversation
| 
           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.  | 
    
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@raftaar1191 Thank you! LGTM, with some minor iterations.
Great catch on the renamed method!
| public function exposePrepareMessagesParamWithSystemInstruction(array $prompt, string $systemInstruction): array | ||
| { | ||
| return $this->mergeSystemInstruction($prompt, $systemInstruction); | ||
| return $this->prepareMessagesParam($prompt, $systemInstruction); | 
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Great catch!
This PR improves the documentation for the abstract base classes in the OpenAiCompatibleImplementation namespace. The updated docblocks now clearly state that these classes are designed for any provider implementing the OpenAI API format—not just OpenAI, but also Anthropic, Google, and others who offer OpenAI-compatible endpoints.
No functional code changes were made; only comments and docblocks were updated for clarity.
This resolves confusion for contributors and maintainers, making it explicit that these base classes are intended for multi-provider use, following the OpenAI API specification as a standard interface.
Notes:
Used AI assistance to update and clarify the documentation for these base classes. No functional code changes were made.