BUG: VSCodeWorkspace Extension

[pjpscriv]

Checks

• I have checked that this issue has not already been reported.

• I am using the latest version of Flow Launcher.

• I am using the prerelease version of Flow Launcher.

Problem Description

Hey gang, apologies this isn't actually an issue for this repo, it's for the VSCodeWorkspace extension. I'm just raising here in the hopes of getting some more attention to this issue because it's one of the main ways I use Flow Launcher.

The extension's been broken for new versions of VS Code for about a month, because of a change to where VS Code stores recent workspaces. The fix is actually pretty easy, and there's a PR that fixes it: taooceros/Flow.Plugin.VSCodeWorkspace#25 . A few people, myself included, have downloaded and built the fixed version and it works perfectly ✅☺️.

All that's left is to merge the PR and publish a new version of the extension. Is there anyone here who'd be able to help with that?

To Reproduce

1. Install VSCodeWorkspaces extension from the plugin store
2. Attempt to use the extension (e.g. with its hokey {)
3. See that the extension shows no results

Screenshots

No response

Flow Launcher Version

2.1.2

Windows Build Number

10.0.26200.8457

Error Log

N/A

[Jack251970]

@taooceros I wonder if you have time to handle that.