Conversation
|
@dkolas I think you initially added this feature. Right now the CLI asks the user to input any ConfigTemplate field that is (1) empty, but (2) defaulted. That means to run some things locally, you have to press every time you type This PR isn't any more right.. it's just a proposed tradeoff: if there's a default value applied, and you're doing Were a user to want to override it, they would supply the What do you think? |
dkolas
left a comment
There was a problem hiding this comment.
I'm indifferent on this one. It's for local debugging, so the dev presumably knows what they did and didn't add defaults for. If you feel like this way is more convenient, go for it!
Right now, the
ship run localuser must positively affirm each default value in configs.This sets behavior to automatically use defaulted values, leaving the user with the
-c config.jsonoption to override defaults.