Change History

[spmeesseman]

Is your feature request related to a problem? Please describe. No

Describe the solution you'd like Ability to view the file's change history, i.e. commit date, author, and comment. Both from Explorer (via context menu) and from the SCM view, in the list of changed files via context menu and/or toolbar icon button.

Describe alternatives you've considered Using Tortoise for this externally

Additional context I may be able to offer my time to work on this if interested, but then again, maybe not. I would lovvvvve this feature as I manage several under-25's and check commits often, so wanted to at least stick it in there in case someone got bored one day

[JohnstonCode]

You can currently do this in the Svn view

[spmeesseman]

jeez i never even noticed that, and i use the file history below that all the time for my selected file in the editor. it would still be super handy to be able to right click a file in Explorer and get this info, so thanks for not closing! lol. i can let you know soon if I think i might have some time to contribute with this at some point

[spmeesseman]

hmmm, for the particular functionality that exists, when i select a file in 'Repositories', it doesnt load in the 'File History'. The file that I currently have open in my editor reamin as the one open in 'File History'. Should it be loaded into that little view when selecting a file in the Repositories file tree?

[JohnstonCode]

Currently it only supports showing the file history of the active editor window.

[JohnstonCode]

This might change when the timeline feature is released.

[spmeesseman]

Thanks, and thanks for all the work on this extension, much appreciated.

i actually whipped up something real quick in that dumb little 'svn-scm-ext' extension i did when I first started using Code, you can check it out and use it if you'd like.

[spmeesseman]

hey can i get off subject and ask real quick too... why do you use 'original-fs' over 'fs' ?

[JohnstonCode]

It is because electron providers origional-fs without asar support. We need it without asar support for people building electron projects in their SVN repos But in VS Code remote it only runs in node so we use the origional-fs package with reverts to using the normal node fs

[edgardmessias]

About original-fs: https://www.electronjs.org/docs/tutorial/application-packaging#treating-an-asar-archive-as-a-normal-file. The original-fs npm package it is a single command:

export default require('fs');

[spmeesseman]

aaaaahhhhhh, thanks! i always wondered