Unable to handle symlinks earlier in destination path hierarchy
ralish opened this issue · comments
For example, assume we're symlinking $HOME\.config\pip\pip.conf
to $HOME\dotfiles\pip\pip.conf
.
If $HOME\.config
is a symlink to $HOME\config
, then an exception is thrown indicating a directory symlink to an unexpected target was found. As the evaluated source path is further up the directory hierarchy than the target source path it should not indicate a failure. Instead, we should retry the operation on each additional possible level in the source path hierarchy until we've truly exhausted all options, at which point an appropriate exception should be thrown.
Support added in v0.5.2 with global setting ($DotFilesAllowNestedSymlinks
) and further improved in v0.5.3 with support for toggling the setting state by cmdlet parameter (-AllowNestedSymlinks
).