All symlinks are treated as directories #4
Description
If I have a remote path that includes a symlink to a file (d.txt) like:
It ends up being treated like a directory in the FTP workspace:
The optimal behavior I would expect would be for the filesystem provider to treat d.txt as a file.
I notice this is also the behavior in some ftp clients, like Filezilla for example:
If this is the underlying implementation, it seems that anything whose type is not File (0) will be treated as a directory. Since Symlinks are type 2, they would be handled in the else block where fileStat.isDirectory is set to true.
Is there some solution to this through the existing API, or is it something that might be handleable in a final API?