Closed kewegner closed 4 years ago
As of yet we have not encountered a problem with symlinks and the watcher. I believe there is an instance in the tooling where they used a symlink, but no problems were reported. At this time, it is unclear if there is a simple solution, should this ever become and issue in the future.
There are two kinds of situations that might encounter an issue.
I wonder if we should just document the fact that symlinks are not supported by the watcher as a known limitation for the moment?
I am working on README comments for this and will have done by Friday.
@rykal-nate are you intending to test this out, or are we just looking to add wording, as if so I'd suggest adding something like:
"The use of symlinks within the directories that the controller monitors for file changes might result in undefined behavior."
to the README?
@helenmasters - Yes, I did a bit of testing yesterday, the behavior is a bit nuanced and not worth documenting every individual scenario IMO. In large, edit actions on sym links are not recognized by the controller such as document edits, renames etc ... however if you deleted a symbolic link on a watched directory there would be a directory event. I think the text you have is sufficient.
I question if this should be documented with the stack env variables possibly or point to this controller notice from that location. @neeraj-laad maybe state its not a best practice to use symbolic links as it relates to changing stack artifacts in addition?
Thanks!
We need to review and discuss this. Question.