-
Notifications
You must be signed in to change notification settings - Fork 17
provided path is invalid #121
Comments
This looks like there is a space at the end of the filename. Is this correct? |
In the log there is a space, but the actual file is without spaces. |
@Newar417 I tried it. With a space at the end, I can create the same exception (and in the log is exactly one space at the end of the filename like in yours). Without a space there, it works correctly. I am going to remove the no space-rule as it's valid to use a space at the end of the filename. Moreover, I will add showing which validation rule caused the exception. It could be that your file has got a space at the end or had it earlier (and the old one is still in the index). |
Edit: attached a fresh error report.
Space is there (again not in the actual file though). |
#122 (which changes the handling of the space) isn't part of a release yet. I try to create a release today. |
As requested from #98 (pasted from the clipboard, detailed report enabled):
The text was updated successfully, but these errors were encountered: