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

Expose uriScheme through vscode.env #71397

Merged
merged 3 commits into from
Apr 2, 2019
Merged

Conversation

rebornix
Copy link
Member

@rebornix rebornix commented Mar 28, 2019

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.

@joaomoreno joaomoreno requested a review from jrieken March 29, 2019 08:37
@joaomoreno joaomoreno added this to the April 2019 milestone Mar 29, 2019
Copy link
Member

@joaomoreno joaomoreno left a comment

Choose a reason for hiding this comment

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

Makes sense.

/**
* The url protocol of the editor, like 'vscode', 'vscode-insiders'.
*/
export const urlProtocol: string;
Copy link
Member

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?

Copy link
Member

Choose a reason for hiding this comment

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

Copy link
Member Author

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.

@rebornix rebornix changed the title Expose urlProtocol through vscode.env Expose uriScheme through vscode.env Apr 1, 2019
@rebornix rebornix requested a review from jrieken April 1, 2019 16:29
@rebornix
Copy link
Member Author

rebornix commented Apr 2, 2019

As we discussed on API syncup, we are going to use the name uriScheme for consistency, so I'm going to merge this PR. We can make tweaks if there are any other feedback.

@rebornix rebornix merged commit 6e66ff6 into master Apr 2, 2019
@joaomoreno joaomoreno deleted the rebornix/expose-url-protocol branch April 3, 2019 13:13
@github-actions github-actions bot locked and limited conversation to collaborators Mar 27, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants