-
Notifications
You must be signed in to change notification settings - Fork 14
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
Same file (different paths) deleted then changed #1278
Comments
I'm seeing the backslashes on deleted on my win git bash, but not the immediate forward slash changed. Also note all of this is happening during watch on pull, none during initial transpilation:
|
I normalized all paths and it seems to be behaving better on my Win git-bash. I'll test on my Mac next. |
Everything seems to be working as expected on my mac. @zepumph can you please take this for a test drive? If it works well, we can tell slack dev-public to pull and restart their transpilers. |
I'm not seeing the issue, thanks for working on this. Do you want to factor out |
Thanks for the recommendation. This will sound like a backtrack, but I feel the best way forward for this issue is to support windows paths on windows. The main reason I normalized out the paths was to make text searching for substrings like 'my/path/element` trivial, but perhaps that should be the part this is abstracted instead of having to remember to call Transpiler.joinPath or forwardSlashify everywhere. Sound ok? |
Yes, it makes sense! Good luck. |
As I was prototyping #1272 it was very convenient to be able to search for substrings in paths like |
The commit adds Transpiler.join, would you like to review? Was mostly straightforward with the more complex usage in |
Looks great! Thanks. |
In the transpiler: There seems to be something that isn't using path.sep and/or forwardSlashify
The text was updated successfully, but these errors were encountered: