-
Notifications
You must be signed in to change notification settings - Fork 27.9k
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
Expose uriScheme through vscode.env #71397
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.
Makes sense.
src/vs/vscode.proposed.d.ts
Outdated
/** | ||
* The url protocol of the editor, like 'vscode', 'vscode-insiders'. | ||
*/ | ||
export const urlProtocol: string; |
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.
Not sure, the thing is called uri-handler, now we talk about url protocol. What's correct? Why being inconsistent? Also protocol vs scheme?
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.
We should also update this https://github.com/Microsoft/vscode/blob/a3fc8198a7a274b580e8fbf7664e13a8bd8df647/src/vs/vscode.d.ts#L6643
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.
We should call it uriScheme
as uriHandler
stands for the application.
As we discussed on API syncup, we are going to use the name |
Right now when extensions attempt to construct a callback url for themselves, they can only guess by checking the appName, but we should be smart enough to expose this information, for example
vscode
,code-oss
,vscode-exoloration
.