-
Notifications
You must be signed in to change notification settings - Fork 17
TypeError: Cannot read property 'toLowerCase' of undefined #94
Comments
@aaroncarsonart: Thanks a lot for reporting, i will take a look why this happens. |
Okay, it seems this happens if the Java-file is placed underneath a symbolic link. This is error seems to pop up since we're not dedicated handling symlinks, as the pathwatcher-API efforts. I am working on a patch. |
Yeah, that makes sense. I can verify the problem file was in a symbolic link directory. |
Thanks for verification - i guess i already have some sort of solution and currently try to figure out how hook into the promised callback chain of hell. I guess you can expect the patch until tomorrow. |
- Add specs for issue AtomLinter#94 - Add test to verify working symlinks as higher directories - Fix Directory-call, add fallback path for getProjectRootDir - Fix links, updated Latest Changes - Add subdirectory to fixtures - Refactor base-specs > getProjectDir's implementation is faulty since it does not proper handle the appearance of symlinks (see :251).
- Add specs for issue AtomLinter#94 - Add test to verify working symlinks as higher directories - Fix Directory-call, add fallback path for getProjectRootDir - Fix links, updated Latest Changes - Add subdirectory to fixtures - Refactor base-specs > getProjectDir's implementation is faulty since it does not proper handle the appearance of symlinks (see :251).
- Add specs - Add test to verify working symlinks as higher directories - Fix Directory-call, add fallback path for getProjectRootDir - Fix links, updated Latest Changes - Add subdirectory to fixtures - Refactor base-specs - Fix issue reference in iss36-spec > getProjectDir's implementation is faulty since it does not proper handle the appearance of symlinks (see :251).
When I create a new file
Test.java
and save it with the following content:I get this stack trace error popup:
The text was updated successfully, but these errors were encountered: