feature(cli): removes the necessity to pass --config to read the default configuration file BREAKING #771
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.
Description
Motivation and Context
As dependency-cruiser is likely used 99.9% of the time with a configuration file, it is more user friendly to be able to run it without having to specify where the configuration file lives, especially if it's on the default location.
This is a 🚨 BREAKING change for the few folks who run dependency-cruiser without a configuration file. Those will have to use the (already existing)
--no-config
command line option in stead.How Has This Been Tested?
Types of changes
Checklist
📖
⚖️