fix: Use WebClient.Builder and RestClient.Builder From Spring Dependency Injection Mechanism for OpenAI. #675
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.
Closes #609
Previously, the code employed WebClient.builder() and RestClient.builder() directly for constructing instances without making use of Spring's dependency injection capabilities.
This direct approach posed limitations, particularly in scenarios where users wished to extend or modify the configuration of WebClient. Unfortunately, due to the direct instantiation, such customization was not feasible.
To address this limitation, the fix introduces a more robust solution by embracing Spring's dependency injection mechanism. By leveraging this capability, configuration and management of these builders are now centralized within the Spring application context. This empowers users to easily extend, customize, or override configurations as needed, enhancing the flexibility and maintainability of the codebase.