| 文件 | 最后提交记录 | 最后更新时间 |
|---|---|---|
[Feature] LynxBase standalone -- Implement Independent Trace Event System in LynxBase This change addresses a critical circular dependency between the lynx-base and lynx-trace libraries. Previously, lynx-base relied on the lynx-trace component for its TRACE_EVENT macros, creating a problematic coupling. Key Changes: 1. Decoupling from lynx-trace: The lynx-base library now includes its own implementation for trace events, removing the direct dependency on the lynx-trace component. 2. Injectable Trace Backend: A new service injection pattern has been introduced. Consumers of lynx-base are now responsible for providing a concrete tracing implementation (a "backend") by implementing the LynxBaseTraceService interface and injecting it at runtime. issue:m-6736726571 AutoSubmit:true | 1 年前 | |
[Feature] LynxBase component uses ServiceAPI to manage Service implementations on the darwin side. After the Service API was moved to a lower layer with independent dependency capabilities, in order to reduce maintenance costs and code redundancy, LynxBase now uses the Service API to manage Service injection and access. AutoSubmit: True | 1 年前 |