I like the Store options, but it would be useful to have the option to store the parameters used for a template along with the code.
Here's the scenario:
At work, we are several working on multiple modules, and we all base our work on a common template.
That template evolves, and we re-apply the newer version of the template onto existing projects to benefits from improvements, while keeping it consistent.
Currently, it's possible to do that by using the -PassThru parameter, and storing the resulting object along with the source code, and invoking the update based on that object later on.
Ideally, Plaster would have a switch parameter to store those parameters as a file within the DestinationPath, and would automatically look for such file and load it as default (overriding user defaults when conflicting), in a similar way the Store currently works.
I like the Store options, but it would be useful to have the option to store the parameters used for a template along with the code.
Here's the scenario:
At work, we are several working on multiple modules, and we all base our work on a common template.
That template evolves, and we re-apply the newer version of the template onto existing projects to benefits from improvements, while keeping it consistent.
Currently, it's possible to do that by using the
-PassThruparameter, and storing the resulting object along with the source code, and invoking the update based on that object later on.Ideally, Plaster would have a switch parameter to store those parameters as a file within the
DestinationPath, and would automatically look for such file and load it as default (overriding user defaults when conflicting), in a similar way the Store currently works.