mrm
mrm copied to clipboard
User-configurable default preset
Allows users to specify their own custom default preset.
In my opinion the strength of mrm
is not the default tasks but the ability to create your own presets and tasks to setup applications and repositories. The default tasks interferes, uses the wrong configuration and is in general incomplete for my purposes. The major issue is that with an organization or company you want more control over the configuration.
By setting my own default preset it is easier to ensure that npx mrm eslint
will setup eslint my way. Actively entering --preset @mycompany/unicorn
is tedious when you want to run it across multiple repositories or when you want to run multiple tasks sequentially (i.e. task, commit, task, commit).
I do recognize that it might be a bit of documentation issue since npx mrm mytask
might to different things on different machines but I hope the changes to output makes it more clear:
Running mytask (from preset "@mycompany/unicorn")...
Codecov Report
Merging #186 (40b32b0) into master (882f9e6) will increase coverage by
0.00%
. The diff coverage is100.00%
.
Impacted Files | Coverage Δ | |
---|---|---|
packages/mrm/src/index.js | 100.00% <100.00%> (ø) |