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

Ensure some degree of backwards compatibility when asking for the references viewlet #152834

Closed
jrieken opened this issue Jun 22, 2022 · 0 comments · Fixed by #153298
Closed

Ensure some degree of backwards compatibility when asking for the references viewlet #152834

jrieken opened this issue Jun 22, 2022 · 0 comments · Fixed by #153298
Assignees
Labels
insiders-released Patch has been released in VS Code Insiders references-viewlet
Milestone

Comments

@jrieken
Copy link
Member

jrieken commented Jun 22, 2022

Ah, sorry for the breakage... I believe asking for both is the best option for now but I can also add a "migration" path into the getExtension implementation, e.g use vscode.references-view when seeing ms-vscode.references-view

Originally posted by @jrieken in #152213 (comment)

@jrieken jrieken self-assigned this Jun 22, 2022
@jrieken jrieken added this to the June 2022 milestone Jun 22, 2022
@VSCodeTriageBot VSCodeTriageBot added the unreleased Patch has not yet been released in VS Code Insiders label Jun 27, 2022
@VSCodeTriageBot VSCodeTriageBot added insiders-released Patch has been released in VS Code Insiders and removed unreleased Patch has not yet been released in VS Code Insiders labels Jun 28, 2022
@github-actions github-actions bot locked and limited conversation to collaborators Aug 11, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
insiders-released Patch has been released in VS Code Insiders references-viewlet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants