akileez
commented
3 years ago The feature set of generate is very appealing, conceptually. My take on generate/generate's feature set for this project?
Features
- flow control: through the use of async/await, @overlookmotel promise-methods and @ricardobeat taks
- render templates: use templates to create new files, or replace existing files
- template engine: use a template engine to render templates, meaning handlebars on a major end or something small and lite, like @terkelg cantinflas on a minor end.
- front-matter: use yaml front matter in templates to define settings or defaults on a file-by-file basis but only if using handlebars?
- data: a method to read/parse data provided by the user for rendering templates, scaffolding and configuring a project.
- config cache: for in memory configuration settings and project-specific defaults. (organization on my part)
- file: a virtual file object using @shannonmoeller ygor/file ...part of the ygor toolset
- git repo: what this project presently does using the command line via
gitand/orhub - and likely no more than this!
Ok, been sitting on this entry for about six hours contemplating the direction of npinit
All of the above "features", with the exception of a git repo, presently exists within an internal project, a complete re-write of rendr.
meguesses (like methinks) this will be the roadmap for coding over the next couple of weeks
At present the focus is on creating a git repo with additional project files, as an after-thought. What if this aspect were reversed and the focus becomes creating projects/files with git repo creation functionality as an add on?
This would be more in-line with my usage patterns (the true reason npinit fell behind the times -- I do not use git that often.)