-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
Code extension registers multiple providers for the rust-analyzer
scheme
#12699
Comments
internal: use different schemes for the custom views Related to #12699, but doesn't fix it because we still register the providers multiple times.
internal: use different schemes for the custom views Related to #12699, but doesn't fix it because we still register the providers multiple times.
internal: use different schemes for the custom views Related to #12699, but doesn't fix it because we still register the providers multiple times.
It's not fixed yet. Originally:
#12702 fixed the first problem, the second still exists. To fix this you'll probably have to extract the |
Thank you. I'll try it. It may take a little while because this is my first time to develop a vscode extension. |
I cannot reproduce the issue. Here are what I did to debug:
export function viewItemTree(ctx: Ctx): Cmd {
// ...
console.log("viewitem"); // I added this line.
ctx.pushCleanup(
vscode.workspace.registerTextDocumentContentProvider("rust-analyzer-item-tree", tdcp)
);
return async () => {
console.log("viewitem async"); // I added this line.
// ...
}
}
Probably I'm wrong but It appears that |
Yes, I think you're right. Sorry for the inconvenience :(. |
From the
registerTextDocumentContentProvider
docs: "Only one provider can be registered per scheme".Two of the providers appear to handle this correctly (
rust-analyzer-status
,rust-analyzer-memory
), we should probably do the same thing in the remaining four places.CC eclipse-theia/theia#9136 (comment)
The text was updated successfully, but these errors were encountered: