-
Notifications
You must be signed in to change notification settings - Fork 30.7k
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
quickopen: file url #190304
base: main
Are you sure you want to change the base?
quickopen: file url #190304
Conversation
@microsoft-github-policy-service agree |
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.
Closed
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.
Closed
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.
Thanks for contributing! I don't think this is the right change. This is adding special logic to extractRangeFromFilter
for file://
but it's not clear that a function called extractRangeFromFilter
would do that.
I don't think this is the right place for this logic. I think the caller of extractRangeFromFilter
or something in quick open code should normalize URIs to just their paths or something like that.
3857f63
to
9c30b2e
Compare
Action: "Go to file..." (
workbench.action.quickOpen
)Example query:
/etc/hosts
Result: found "file results"
Example query:
file:///etc/hosts
Result (expected): found "file results"
Result (actual): "No matching results"
VSCode supports opening
file://
url with selection, e.g. when clicking such links in editor.P.S. I often copy
file://
urls from chrome to open them in vscode