Summary
Create deprecation plan for native logger_system::log_level API in favor of common::interfaces::log_level.
Part of #317
What (Problem)
The logger class has dual API:
- ILogger interface using
common::interfaces::log_level
- Native API using
logger_system::log_level
This creates confusion about which API to use.
Why (Rationale)
- Single source of truth: One log_level type reduces confusion
- Interface compliance: Align with common_system interfaces
- Future compatibility: Prepare for major version migration
How (Solution)
- Mark native
log_level methods as [[deprecated]]
- Document migration timeline
- Add deprecation warnings
- Plan removal in next major version
Acceptance Criteria
Labels
- refactor
- api-design
- deprecation
Summary
Create deprecation plan for native
logger_system::log_levelAPI in favor ofcommon::interfaces::log_level.Part of #317
What (Problem)
The logger class has dual API:
common::interfaces::log_levellogger_system::log_levelThis creates confusion about which API to use.
Why (Rationale)
How (Solution)
log_levelmethods as[[deprecated]]Acceptance Criteria
Labels