-
-
Notifications
You must be signed in to change notification settings - Fork 194
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
When advising user to file a bug, should mention the file it was trying to format #726
Comments
Hello @penelope99, thanks for reporting this. We should definitely tell the user what file caused the problem. |
I believe this is happening because of the way errors are reported in the CLI. One of these functions gets called, depending on the CLIs input
@penelope99 tried to recursively format a directory while formatting the files in place, rather then storing the formatted copy somewhere else (i.e. no The bug might be in this branch of the else case, because the Some approaches to solve this problem:
Regarding the second approach, that exception is being thrown by the I hope this helps. |
Another instance of this same problem:
|
@penelope99 , that last one might be unrelated to the CLI input. |
"That file"? But I still don't know what files are failing. |
Oh, sorry, I though I mentioned this already. The first time my three files a,b and c were formatted correctly and the second time I added an error in b. Nevertheless you can still see that |
I've tried to format a whole solution with
--recurse
, and received several errors of this type:This error message should include the file name or file path that it was trying to format, so that I can report an issue with better context, I assume.
The text was updated successfully, but these errors were encountered: