-
-
Notifications
You must be signed in to change notification settings - Fork 65
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
Rewrap started failing? #11
Comments
I closed some tabs and opened some other tabs, and it started working again. I'll leave the issue open in case you want to debug further... |
Thanks for reporting. Unfortunately I can't really tell anything from that; it's all just vscode's own code. I'll leave this open for a while in case you or anyone else has the same problem and we can work on reproducing it, and I'll add some more logging code into the next version to try to diagnose any errors that occur. |
Hi @stkb, I think I'm running into this issue. I'm on VS Code 1.6.1 (rolled back from 1.7), macOS Sierra 10.12.1, and rewrap 0.6.2 Here's the log:
I can only reproduce it in one file right now, a compiled version of https://github.com/Microsoft/vscode/blob/master/src/vs/editor/contrib/goToDeclaration/common/goToDeclaration.ts. Thanks for the great plugin. |
@nicot Thanks, that helps a lot, but I'm having trouble reproducing. Could you upload the exact file that it errors on (you can attach a file to a comment here), and tell me which comment in it you're trying to wrap? |
Here's a gist with the failing code/line: https://gist.github.com/nicot/aed1b230392ec2a3bcdc7b2ac970f653#file-gotodeclaration-js-L321. It blows up on every line I've tried in that file though. |
Perfect! thanks. In that file, it's the empty |
Have just published v0.6.3 which hopefully fixes the issue (have tried on vscode 1.6.1 and 1.7.1). Could you update and confirm? |
Works perfectly now! Thanks a bunch for quick the fix and the great plugin. |
Great! Thanks for the help |
Mac OS El Capitan 10.11.4, VS Code Version 1.5.2 (1.5.2), Rewrap 0.6.0
The text was updated successfully, but these errors were encountered: