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).
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).