You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
scaffoldStream: instead of writing the files to the files system, we should just update a dest property or something similar on the file object, using resolved path information from the scaffold options. Then we can just return a source stream and use .dest() to write the files to the specified dests - or modify the dest if we want
ability to process specified targets on the scaffold. this would be easier if we handled the scaffold config internally and exposed a .generate method on the scaffold - which would take a target name and options, or a dest and a context, etc. we'll need to discuss
automatically create tasks from targets
The text was updated successfully, but these errors were encountered:
I think we should also have targets/scaffolds support the "conventional" assemble template collections: pages, partials, templates. so it would be easier to build boilerplates or complex things that have templates that need to be rendered
e.g somehow these things need to be able to find other templates and render them...
scaffoldStream
: instead of writing the files to the files system, we should just update adest
property or something similar on the file object, using resolved path information from the scaffold options. Then we can just return a source stream and use.dest()
to write the files to the specified dests - or modify the dest if we want.generate
method on the scaffold - which would take atarget
name and options, or adest
and a context, etc. we'll need to discussThe text was updated successfully, but these errors were encountered: