microsoft / microsoft/amplifier
Cleanup: Migrate remaining modules off config_compat.py in amplifier-app-cli
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 3.1k
- Forks
- 261
- Avg merge
- 3h 28m
- Merged PRs (30d)
- 13
Description
Background
As part of the AppSettings consolidation (app bundle feature), we migrated most code to lib/settings.py. However, several modules still depend on lib/config_compat.py:
Files Still Using config_compat
paths.py- ConfigManager, ConfigPaths, Scopeprovider_manager.py- ConfigManagermodule_manager.py- ConfigManagerprovider_loader.py- ConfigManagerprovider_sources.py- ConfigManager
Task
Migrate these modules to use lib/settings.py AppSettings instead, then delete config_compat.py.
Notes
config_compat.pyheader already says: "New code should use lib/settings.py AppSettings instead"- This is a lower-priority cleanup task
Repository
amplifier-app-cli
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by comparing lib/config_compat.py with lib/settings.py and AppSettings. Then inspect paths.py, provider_manager.py, module_manager.py, provider_loader.py, and provider_sources.py to trace their current configuration use. Done means those modules use AppSettings and config_compat.py can be deleted.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- cli, tooling
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 45/100