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
Git: Investigate using vscode.open
and vscode.diff
as commands in scm
#110397
Comments
I landed my changes, if an extension is using To adopt this in SCM, we need something similar like this code right before we invoke the command of a SCM tree item: vscode/src/vs/workbench/contrib/views/browser/treeView.ts Lines 468 to 475 in 630e706
The fact that this is currently hardcoded inside |
Thanks @bpasero, looks awesome! |
@bpasero Check it out: ed4d86e#diff-a29d112f7e1fecae5536543510588375d7283d06e96a4cf64325e8b600f30356R1940-R1941 It is mostly working with some very weird behavior, on which I will need your help next week: |
@eamodio Let me know if you'd like a tour of these changes, since they are deep. |
Currently SCM has a custom mechanism for opening resources: SCM providers provide a command for each resource (git provides
git.openResource
) and it does some magic behind the scenes to be sure that command gets passed the right Resource when invoked. But this custom approach can never align with all the UI gestures and settings related to editor opening actions (preview, to side, etc).We should investigate whether its feasible for git to simply provide
vscode.open
andvscode.diff
as the Resource opening commands. That way the core can gives us all the preview, open to side, features.Related:
The text was updated successfully, but these errors were encountered: