Included and excluded changes are not persisted when changing folders about azure-repos-vscode

[jeffyoung]

Hi @pderks, thanks for trying out the extension (and thanks for the detail)!

Yes, today, the 'excluded' group is simply held in memory since there's no way to inform TFVC to 'exclude' those files at the command line. The files that are in the included list have had some TFVC command run on them and they're not in the excluded list. That's why those get persisted (TFVC knows about them).

So I'm sure I understand, you've opened these folders in VS Code (using Open Folder...) correct? In that case, each time you open the folder the extension is re-initialized (which is by design). I just want to ensure I understand your scenario.

One thing I had considered was storing some of this state in either workspaceState or globalState with the ExtensionContext object. Maybe I could do that at some point.

[pderks]

@jeffyoung Yes, that is an accurate description of the scenario. I like your idea of a workspace state or global state. I believe it would be a helpful feature especially when working with multiple projects at the same time.