Configure watch via .amber.yml#996
Conversation
…d wording of messages
…mplate for details); rewrote ProcessRunner to handle any generic task that can be specified by a set of build and run commands and a set of globs to include and exclude; removed unused build_args and run_args args
|
@anamba thanks for doing this, it's long overdue and will be a welcome change to the workflow.
This is a great thing to discuss. Can you explain what you mean by that? Are there existing tools which Amber can wrap or depend on that you have experience with? I think previously Amber depended on another shard, which I believe was abandoned/absorbed. |
Nah, I didn't have anything in mind, I just mentioned that for the sake of completeness (answering the question). I think you're referring to Sentry (which is still around). I saw some references to Sentry in there as I was working on this. I do use Guardian for specs sometimes (but now that won't be necessary for amber projects). The main advantage provided by |
|
@anamba Thanks you so much for this! 💯 I think we should document this here: https://docs.amberframework.org/amber/cli/watch Related issue: amberframework/docs#121 |
Description of the Change
Allow user to configure
amber watchfrom.amber.yml. Configuring this way is optional (there is still a default config, and it is the same as before), and you can continue to use the command line switches if you want (if you have a config in.amber.yml, command line switches will override it).A sample
.amber.yml:Alternate Designs
The config is too complex to configure solely via command line switches/arguments, and leaving it non-user-configurable is creating unhappiness among users.
Benefits
Developers are now free to choose
yarnovernpm, or even nothing at all. Additionally, they can useamber watchto run other processes as well.Possible Drawbacks
Mainly some code bloat. It's certainly possible that this is not something the amber project should handle directly.