Currently, we always create a temporary directory called the "template directory," and copy the template contents into that directory. This makes sense when the template is a remote (e.g. a github repo), but is perhaps unnecessary when the template is just stored in a local directory.
The LocalDownloader could perhaps be replaced by a no-op that just points to the existing template files that are already on the filesystem. Currently the LocalDownloader copies the files into the template directory (a temp dir) for no great reason.
Before we do this, we'll want to be sure that we never modify the template directory. Because it's OK to modify our private temp dir copy of the template, but it's not OK to modify any files outside of temp dirs that are owned by the user.
Currently, we always create a temporary directory called the "template directory," and copy the template contents into that directory. This makes sense when the template is a remote (e.g. a github repo), but is perhaps unnecessary when the template is just stored in a local directory.
The LocalDownloader could perhaps be replaced by a no-op that just points to the existing template files that are already on the filesystem. Currently the LocalDownloader copies the files into the template directory (a temp dir) for no great reason.
Before we do this, we'll want to be sure that we never modify the template directory. Because it's OK to modify our private temp dir copy of the template, but it's not OK to modify any files outside of temp dirs that are owned by the user.