feat: Support command selection with the config command #22
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What type of PR is this?
feat: The
config
command is great for centralizing nwa configuration in a project. It is weird though that the command being executed is part of the configuration. My expectation for theconfig
command would be to use pre-set paths, template, skip rules, etc. so one could runadd
/update
manually andcheck
in CI using the same configuration. Since YAML doesn't support importing currently one has to copy/paste configuration files for each command being executed.This change adds
-c
and--command
switches to thecheck
command that can overwrite the default command. The priority order, low to high, is the default:add
, the command line flag and what is configured in the config file with the highest priority.Check the PR title.
(Optional) More detail description for this PR.
Test plan:
Which issue(s) this PR fixes:
Fixes #21