Update visual-studio-code extension

[Nenuial]

Description

Screencast

Checklist

• I read the extension guidelines
• I read the documentation about publishing
• I ran npm run build and tested this distribution build in Raycast
• I checked that files in the assets folder are used by the extension itself
• I checked that assets used by the README are placed outside of the metadata folder

Closes #16400 and closes #16208.

[raycastbot]

Thank you for your contribution! 🎉

🔔 @thomaspaulmann @iainsimmons @macbookandrew @cy-98 @immint023 @pernielsentikaer @vimtor @tonka3000 @aka-rabbi-inv @oilbeater @QIanGua @hakob8956 @erics118 @tmwrnr @tleo19 @aeither @yug2005 @VatsalSy @Tarocch1 @list-jonas @xilopaint @lacherogwu you might want to have a look.

You can use this guide to learn how to check out the Pull Request locally in order to test it.

Due to our current reduced availability, the initial review may take up to 10-15 business days

[Nenuial]

This is my attempt to add support for Positron to the Visual Studio Code extension. I have tested all commands with Positron and they seem to work fine. I am however not particularly familiar with the extension and I might have missed something.

This adresses #16208 and #16400.

[list-jonas]

Seems like cliPath is missing. Are you sure that installing Positron extensions works?

You could also add positron as a keyword.

It also seems to be missing from the preferences.

[xilopaint]

@Nenuial You forgot to add the bundle id in src/utils/editor.ts

[Nenuial]

Thank you for you comments.

I have added the cliPath, keyword and bundleId. I didn't understand what you meant by:

It also seems to be missing from the preferences.

I have added Positron as an option for the build value in package.json. Am I missing something?

[list-jonas]

I was referring to
extensions/visual-studio-code-recent-projects/src/preferences.ts

[greptile-apps]

PR Summary

This PR adds support for Positron, a VS Code-based IDE used by data scientists, to the Visual Studio Code extension.

• Added Positron to the VSCodeBuild enum in src/types.ts to support it as a selectable editor option
• Added Positron's CLI path (/Applications/Positron.app/Contents/Resources/app/bin/code) in src/lib/vscode.ts
• Added Positron's bundle ID (com.rstudio.positron) to the bundleIdMap in src/utils/editor.ts
• Added Positron to the NewWindowMenuItemIndex in src/open-new-window.ts with value 3
• Missing entry for Positron in the buildSchemes object in src/lib/vscode.ts which could cause issues with extension directory access
• Added a new changelog entry at the top of CHANGELOG.md with the required {PR_MERGE_DATE} template

_{💡 (3/5) Reply to the bot's comments like "Can you suggest a fix for this @greptileai?" or ask follow-up questions!}

_{6 file(s) reviewed, no comment(s)
Edit PR Review Bot Settings | Greptile}

[pernielsentikaer]

Did you correct the last things here?

[Nenuial]

I was referring to extensions/visual-studio-code-recent-projects/src/preferences.ts

I'm sorry but I don't see anything in that file that would need to be changed to account for the addition of Positron as a additional build. But again, I'm not that familiar with this extension.

The AI review pointed to a missing entry in buildSchemes. I have fixed that.

[pernielsentikaer]

@list-jonas can you help?

[list-jonas]

I mistakenly referenced a feature removed in the last commit. Please disregard that reference—sorry for any confusion!

[pernielsentikaer]

Hi 👋

Looks good to me, approved 🔥

[github-actions]

Published to the Raycast Store:
https://raycast.com/thomas/visual-studio-code

[raycastbot]

🎉 🎉 🎉

Such a great contribution deserves a reward, but unfortunately we couldn't find your Raycast account based on your GitHub username (@Nenuial).
Please link your GitHub account to your Raycast account to receive your credits and soon be able to exchange them for some swag.