Request: Shared state for ArchConfigHandler to allow configuration overrides
Maintainers usually reply within 2 days
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Quiet
- Tech stack
- python
- Domain
- operating-systems
Research direction
Start by locating ArchConfigHandler and the guided installer entry point, then trace where handler instances are created and configuration files are read during the installation lifecycle. Compare the requested singleton and injection approaches with the existing plugin or external-hook flow. Done means configuration changes persist across the lifecycle and the chosen architectural direction is covered by tests.
Written by the indexing model from the issue text.
Description
describe the request
Currently, each instance of the class ArchConfigHandler instantiates and reads configuration files independently. This behavior prevents plugins or external hooks from modifying the configurations processed by the guided installer in real-time. Is it possible to implement this class as a singleton or inject the instance of the handler into the installer instance so that modifications are persisted across the installation lifecycle?
I'm open to submitting a PR if we can agree on the architectural direction (Singleton vs Injection).
- Dominant language
- Python
- Stars
- 8.5k
- Forks
- 774
- Avg merge
- 4d 17h
- Merged PRs (30d)
- 30
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
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.
More from archlinux/archinstall
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
archlinux/archinstall#4807 ·
Maintainers usually reply within 2 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
archlinux/archinstall#4603 ·
Maintainers usually reply within 2 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
archlinux/archinstall#4385 · 2 comments ·
Maintainers usually reply within 2 days
-
Difficulty 5/5 Over a week Newbie friendliness 30/100
archlinux/archinstall#4813 ·
Maintainers usually reply within 2 days
-
Difficulty 3/5 1-2 days Newbie friendliness 45/100
archlinux/archinstall#4808 ·
Maintainers usually reply within 2 days
All issues in archlinux/archinstall
Similar issues
-
tool-calling
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
vllm-project/vllm#59838 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 92/100
raullenchai/Rapid-MLX#4042 ·
Maintainers usually reply within 1 day
-
documentation
Difficulty 1/5 Under an hour Newbie friendliness 92/100
transitmatters/mbta-slow-zone-bot#70 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
litestar-org/advanced-alchemy#811 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day