-
Notifications
You must be signed in to change notification settings - Fork 588
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ChangeWatcher.WatchChanges works only with absolute file patterns #780
Comments
I didnt intend for absolute paths to be required, I'll take a look at fixing this. |
IsMatch is supposed to work exactly like the existing glob implementation, except not requiring directory traversal to check for a match. Any differences in behavior I would consider a bug. |
I made FileInclude add its base directory to the glob pattern when calling is match. Fixed in #782 |
@voiceofwisdom could you please take a look at fsprojects/Paket#811 I have very strange behaviour.
==> The watcher starts to build the docs, but it goes into endless loop since it wrongly (?) detects edits in other content files (which I didn't change or save) |
I also have issues with relative paths. Don't know if it is same issue. I have FAKE project in D:\Projects\fake_test\fake_test\fake_test with build.fsx
But when I use absolute path: D:/Projects/fake_test/watch_folder/, it works fine. I created sample project to reproduce the issue: https://github.com/marisks/fake_test |
The watcher uses an alternative implementation of the globbing syntax. It does not support relative paths as it stands. 😞
|
For now I am just using Path.GetFullPath as a workaround: let fullDir = Path.GetFullPath relativeDir |
The original issue seems to be fixed. Can someone open a new issue for the part which is still open (and explain what the issue is)? |
Verified by this test case in
GlobbingSpecs.cs
:Appending FAKE's
currentDirectory
to the pattern isn't a big deal, but then we should reflect this in the docs, because the tutorial shows a non-working sample. The api docs are correct./cc @voiceofwisdom
The text was updated successfully, but these errors were encountered: