Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Make registerDiffInformationCommand public
See original GitHub issueI see that the registerDiffInformationCommand has been propsed for a while. I was wondering if you have an eta for when it will be stable. The selected ranges functionality would be useful.
Issue Analytics
- State:
- Created 4 years ago
- Reactions:8
- Comments:5 (3 by maintainers)
Top Results From Across the Web
"Fossies" - the Fresh Open Source Software Archive
registerDiffInformationCommand (commandId, command); 371 } else ... showWarningMessage(l10n.t('This will create a Git repository in "{0}".
Read more >Fossil SCM provider for VSCode: Changes On Branch develop
DOCTYPE svg PUBLIC "-//W3C//DTD SVG 1.1//EN" ... registerDiffInformationCommand(commandId, command); // } else { return commands.
Read more >TypeScript vscode commands.executeCommand Examples
TypeScript commands.executeCommand - 30 examples found. These are the top rated real world TypeScript examples of vscode.commands.
Read more >TypeScript commands.executeCommand方法代码示例
public CallEditorCommand(argument: string) { vscode.commands. ... VSCode saves all files. we should do the same //before running a quick compile, ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Any updates on this? I wanted to implement a ‘revert change’ button for perforce but realised the API isn’t available yet
edit: also, the idea of having the overall diff information available could be useful for providing inline annotations (like GitLens line blame)
I’d say that API is a hack and we won’t ever make it public in that form. Tho, there have been idea to make this “proper” by attaching diff-information to editors