Add layered configuration resolver#289
Merged
Merged
Conversation
merge_patch merges two docs, config_sync is last-write-wins, and AssetStore is flat per environment — none compose an ordered defaults < file < env < CLI precedence stack with a deep merge or report which layer won each key. Add LayeredConfig (add_layer / resolve / get / explain) and a standalone deep_merge. Layers are caller-supplied mappings, so the env layer is passed in rather than read from os.environ. Wired through facade, executor (AC_resolve_config / AC_explain_config), MCP, and the Script Builder with a headless test batch and EN/Zh docs.
Up to standards ✅🟢 Issues
|
| Metric | Results |
|---|---|
| Complexity | 43 |
| Duplication | 0 |
NEW Get contextual insights on your PRs based on Codacy's metrics, along with PR and Jira context, without leaving GitHub. Enable AI reviewer
TIP This summary will be updated as you push new changes.
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
What
Adds an ordered, deep-merging config resolver with per-key provenance.
merge_patchmerges two docs,config_syncis last-write-wins, andAssetStoreis flat-per-env — none compose adefaults < file < env < CLIprecedence stack or report which layer won each key.LayeredConfig.add_layer(name, mapping, priority=None)— higher priority wins (default: insertion order).resolve()— deep-merges all layers (nested dicts recursively, scalars/lists replaced).get(dotted_key, default)andexplain(dotted_key)→SourceTrace(value, layer).deep_merge(base, override)— standalone helper.Layers are caller-supplied mappings (env passed in, never
os.environimplicitly), so resolution is deterministic.Layers
utils/layered_config/(pure stdlibcopy, zero PySide6).__all__.AC_resolve_config,AC_explain_config.ac_resolve_config,ac_explain_config(read-only).test/unit_test/headless/test_layered_config_batch.py(9 tests, no Qt).v81_features_doc.rst(EN + Zh) + toctrees + 3 README What's-new sections.Verification
pytest test/unit_test/headless/test_layered_config_batch.py→ 9 passed.ruff check je_auto_control/clean; pylint 10.00/10; bandit clean; radon CC clean.