Is there an existing issue for this?
Current Behavior
The pluggable logger documentation (feature_logging.rst) contains two stale references to the deprecated config/override/ mechanism:
- A "Step 2" section instructs users to enable a custom logger by creating src/config/override/logger.json — this path and mechanism were deprecated in v0.14.0.
- The troubleshooting section lists src/config/override/logger.json as the expected config location for the framework bundle.
Expected Behavior
All references should point to src/local/config/logger.json, which is the current mechanism for configuring the framework logger (introduced in v0.14.0).
Steps To Reproduce
No response
Channel
CURRENT
Relevant log output
Is there an existing issue for this?
Current Behavior
The pluggable logger documentation (feature_logging.rst) contains two stale references to the deprecated config/override/ mechanism:
Expected Behavior
All references should point to src/local/config/logger.json, which is the current mechanism for configuring the framework logger (introduced in v0.14.0).
Steps To Reproduce
No response
Channel
CURRENT
Relevant log output