-
Notifications
You must be signed in to change notification settings - Fork 20
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
Can't convert 'NoneType' object to str implicitly #7
Comments
What operating system are you using? Does the error output provide a line number or stack trace or anything that can help track it down in the formatter? For these sublime plugins I'm much more likely to accept PRs that fix an issue than to actually get in there to get it sorted out. Perhaps by looking at the code and this error you might be able to track it down a bit more. |
Thanks for replying, @TheSavior. Mac OS X 10.11, and no, sorry it didn't include line numbers or any other information. I have SublimeLinter debugging enabled. Does ESLint-Formatter have any similar config to enable more verbose error output? I'm afraid I don't know python, and would only cause more harm than good if I went mucking through the code. Sorry. |
I have same issue. OSX 10.11.5 , sublime build 3114 . I installed the plugin , click the "ESlinkt formatter" > "format this file" and the error comes in the console.
I cant get any more detail information because there's no more detail i could get. I think it would be better if you could print the stacktrace in your error handler function .
|
Any news on this issue? OS X 10.12.1 (16B2657) Console output
|
I would be happy to accept a pull request if someone can figure this out |
This seems to happen when the plugin doesn't have a file to process. I notice it when I save a file, get sublime linter warnings on save, and run the formatter with the warnings still displayed. If I simply close the warnings so the file has focus again, the formatter runs fine. I get the same error with any other sublime popup open, like Ctrl+P or Ctrl+Shift+P, and also if I run the formatter with an empty column focused. Hope this helps narrow it down in case someone wants to look into a solution. |
In OSX I fixed it by removing my custom config of |
I installed this today, and I really like it! However, I keep getting errors like these. What additional debug information can I provide to help resolve this issue?
This is the eslinter output:
The text was updated successfully, but these errors were encountered: