With earlier workaround in root cmd (not passing DefaultNodeHome to depinject), it created a config/client.toml wherever the laconicd CLI was being run
Unset clientCtx.HomeDir and clientCtx.KeyringDir while providing client context to depinject instead to prevent this and still handle the --home flag precedence issue
When using default home directory, all commands still work as DefaultNodeHome is passed to the command executor
Part of #33
Follows PR #34
- With earlier workaround in root cmd (not passing `DefaultNodeHome` to depinject), it created a `config/client.toml` wherever the laconicd CLI was being run
- Unset `clientCtx.HomeDir` and `clientCtx.KeyringDir` while providing client context to depinject instead to prevent this and still handle the `--home` flag precedence issue
- When using default home directory, all commands still work as `DefaultNodeHome` is passed to the [command executor](https://git.vdb.to/cerc-io/laconic2d/src/branch/main/cmd/laconicd/main.go#L18)
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Part of #33
Follows PR #34
DefaultNodeHometo depinject), it created aconfig/client.tomlwherever the laconicd CLI was being runclientCtx.HomeDirandclientCtx.KeyringDirwhile providing client context to depinject instead to prevent this and still handle the--homeflag precedence issueDefaultNodeHomeis passed to the command executor