I noticed a bug (or at least a bug to me :wink:) where if the template engine is asked to process a file that is a symlink to a template, the template engine thinks the symlink is a binary file and skips it, when it should probably follow the symlink to see if it is actually a templated text file or a binary file.
My particular use case is that some files in my dotfiles repo are symlinks to other files in the repo, which happen to be templated. When dotdrop installs the dotfiles for that directory containing symlinks, it wasn't templating the files pointed to by the symlinks because it wasn't following the symlink.
coverage: 91.049% (+0.06%) from 90.987% when pulling ee653e007cb27a18cba7d2dde99bf17ab5b190ea on jtt9340:follow-symlinks into a2de4cfb0c2b143559799858df4c3ab0851fe769 on deadc0de6:master.
I noticed a bug (or at least a bug to me :wink:) where if the template engine is asked to process a file that is a symlink to a template, the template engine thinks the symlink is a binary file and skips it, when it should probably follow the symlink to see if it is actually a templated text file or a binary file.
My particular use case is that some files in my dotfiles repo are symlinks to other files in the repo, which happen to be templated. When dotdrop installs the dotfiles for that directory containing symlinks, it wasn't templating the files pointed to by the symlinks because it wasn't following the symlink.