search

mrcrowl / vscode-hg

Integrated Mercurial source control for Visual Studio Code
MIT License
71 stars 37 forks source link

Support Evolve #114

Closed hdpoliveira closed 4 years ago

mrcrowl commented 4 years ago

Just adding my 2c here.

I would argue that the purpose of the vscode-hg extension is to provide the core features of mercurial as a convenience, rather than to be a fully-fledged mercurial GUI.

The evolve extraction, as it is described is experimental. To my thinking, the commands it provides should be rarely needed and could be run from the command line.

hdpoliveira commented 4 years ago

Yeah I think you're right...

hdpoliveira commented 4 years ago

The point of having support to evolve is that users who use it depend a lot on it, to the point that they consider it as core (I am one of those :smile: )

I'll try to observe how often I need to use evolve commands/features and reflect on this a bit.

I agree that we should NOT try to be a fully-fledged mercurial GUI.

mrcrowl commented 4 years ago

One option that you might consider is to make vcode-hg itself extensible, and then write a separate extension for the advanced Mercurial usage.

VS Code provides a way to access the API of another extension. See the relevant docs here. Also see the extension manifest for details about extensionDependencies.

hdpoliveira commented 4 years ago

Nice!

incidentist commented 4 years ago

Yeah, that's what the git extension does and the api it exposes is used by extensions like GitLens. I would like to do this to make something like GitGraph for hg, that would use the api exported by this extension.

hdpoliveira commented 4 years ago

I'll close this issue then! Thanks for your inputs!