sunnysabor commented on issue #7381: URL: https://github.com/apache/shenyu/issues/7381#issuecomment-5930165922
Initial code inventory: `OpenAiProtocolAdapter` currently lives in `shenyu-plugin-ai-common` and imports Spring AI’s `ChatCompletionRequest`; `AiProxyPlugin` and `AiProxyExecutorService` also pass Spring AI types through, and the common module pulls in Spring AI dependencies. ShenYu SPI follows `@SPI` / `@Join` with `ExtensionLoader`. A clean provider-neutral boundary may need either a small `shenyu-plugin-ai-api` module for models/contracts, or moving the OpenAI adapter into `ai-proxy` so `ai-common` can become dependency-neutral. For #7381, do maintainers prefer a new API module or the latter refactor? I’ll hold the public contract shape until there is alignment. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
