Create CLI for Automock for easy initialization #197
Description
Is there an existing issue for this?
- I have searched the existing issues
Is your feature request related to a problem? Please describe it
Not a real problem.
Describe the solution you'd like
Since Automock 2.0 was released, users have been instructed to independently install two packages: a testing framework and a DI framework. Instead, we can make a CLI that's part of the automock npm package (the developer of which was kind enough to let us take it for our project 🚀 ). To save time, I'll just show you a GIF of the action instead of describing it.
What is the motivation / use case for changing the behavior?
To avoid users mistakes and for better exprience. Also, we might want to implement a functionality that applies some settings to the package.json file (see #193)