Recently in #3 @tylersticka mentioned it would be nice to simplify the syntax of our new tasks:
This may not be possible/feasible, but in a perfect world...
npm run new: Asks what new thing you want to make.
npm run new pattern
npm run new prototype
This PR achieves this by doing the following:
Creating a "new" task and associated npm script
Allow passing a --type param to the npm script which gets passed to the "new" task
Making the existing pattern and prototype tasks into async functions instead of gulp tasks (I originally wanted to keep them as gulp tasks but ran into a lot of road blocks with that approach)
Move these async functions to a new generators directory. This will house similar files, and allow us to store reusable chunks of the generators there.
Recently in #3 @tylersticka mentioned it would be nice to simplify the syntax of our new tasks:
This PR achieves this by doing the following:
--typeparam to the npm script which gets passed to the "new" taskpatternandprototypetasks into async functions instead of gulp tasks (I originally wanted to keep them as gulp tasks but ran into a lot of road blocks with that approach)generatorsdirectory. This will house similar files, and allow us to store reusable chunks of the generators there.removeExamplesnpm script for consistency.Fixes #3