Problem Statement
Currently the application support global configuration load through ~/.lazynx file. It should also support for workspace scope as well, overwriting any default or global configuration for lazyNx in the current workspace.
Proposed Solution
The current config.LoadConfiguration() should be used and adapt the current implementation for this.
Alternatives Considered
Load the workspace path needs to be happens before loading the configuration so can use any .lazynx file in it. Since few logs happens during the workspace prompt, somehow, they need to be saved in runtime before creating the Logger which requires the configuration.
Checking runLazyNX at root.go will help to understand the consideration.
Would you be willing to contribute this feature?
Problem Statement
Currently the application support global configuration load through
~/.lazynxfile. It should also support for workspace scope as well, overwriting any default or global configuration for lazyNx in the current workspace.Proposed Solution
The current
config.LoadConfiguration()should be used and adapt the current implementation for this.Alternatives Considered
Load the workspace path needs to be happens before loading the configuration so can use any
.lazynxfile in it. Since few logs happens during the workspace prompt, somehow, they need to be saved in runtime before creating the Logger which requires the configuration.Checking
runLazyNXatroot.gowill help to understand the consideration.Would you be willing to contribute this feature?