-
Notifications
You must be signed in to change notification settings - Fork 234
Fix issue with reference code lens not working with UNC paths #908
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
Fix issue with reference code lens not working with UNC paths #908
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM I could use a more descriptive comment in the place I mentioned
I changed the code enough to warrant another review. The Windows code path is a bit more complicated but it avoids having to do inserts later by appending chars as required from the start. Although the |
Due to constant crashing with UNC PS1 files, I've rolled back to PowerShell-1.11.0.vsix and have disabled auto updating. It's been constantly poor code quality that is super disappointing with this extension all around the last four months. |
db9dd7e
to
0a89523
Compare
…hell#908) * Fix issue with reference code lens not working with UNC paths * Refactor to avoid extra Insert ops. Simplifies macOS/Linux code path. * Still need to unescape / on macOs & Linux * Replace compile-time check for .NET Core with runtime check
…917) * Fix issue with reference code lens not working with UNC paths * Refactor to avoid extra Insert ops. Simplifies macOS/Linux code path. * Still need to unescape / on macOs & Linux * Replace compile-time check for .NET Core with runtime check
Fixes a few of the failure modes (related to UNC paths) for PowerShell/vscode-powershell#1830