-
Notifications
You must be signed in to change notification settings - Fork 29.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
Support editor labels on non-file scheme "files" #64697
Comments
@isidorn is this covered with the proposed API |
@bpasero no. I mean the extension can register the formatting rules as @eamodio probably already does. But the issue here is what @eamodio points out, you are using the |
@isidorn got it, this is probably something we should look at |
@bpasero I can look into it. Are there some caveats that I am missing, or we simply need to add the |
@isidorn each editor input has a I feel like we should use the same as for resource inputs for name, description and title to be consistent. |
Related to 4e3f58f#diff-81002b6983f6ca938fb1efc58cd9da2f from #55110 (comment)
I am trying to add a custom label to
gitlens
scheme files (to add the revision info), but it looks like labels only work for editors that are instances ofResourceEditorInput
See
https://github.com/Microsoft/vscode/blob/e444eaa768a1e8bd8315f2cee265d725e96a8162/src/vs/workbench/services/editor/browser/editorService.ts#L549-L586
And since the
gitlens
scheme is a registeredFileSystemProvider
it seems to be treated as aFileEditorInput
Can labels be supported on non-
file
scheme "files"?Also this new label was only added to
vscode.open
, can it be added towindow.showTextDocument
as well?/cc @joaomoreno
The text was updated successfully, but these errors were encountered: