Skip to content
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 unicode character uri bug #1143

Merged

Conversation

TylerLeonhardt
Copy link
Member

Fixes PowerShell/vscode-powershell#2324

This removes any usage of Uri.ToString() and creates a worspaceService.GetFile( that takes a Uri to better abstract this away.

This also revs the Omnisharp lib that contains my fix that also removes usages of Uri.ToString()

Copy link
Contributor

@rjmholt rjmholt left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks like a nice cleanup of some unwanted paths-as-strings as well as the fix.

LGTM

@TylerLeonhardt
Copy link
Member Author

Codacy Here is an overview of what got changed by this pull request:

Issues
======
+ Solved 2
           

Clones added
============
- src/PowerShellEditorServices/Services/Workspace/WorkspaceService.cs  2
         

See the complete overview on Codacy

@TylerLeonhardt TylerLeonhardt merged commit 5f1253e into PowerShell:master Jan 8, 2020
@TylerLeonhardt TylerLeonhardt deleted the fix-unicode-character-uri-bug branch January 8, 2020 21:19
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

LSP services fail with non-ASCII characters in paths
2 participants