Minor VSCode QOL Improvements

[Piras314]

About the PR

I added Tools & Release run configurations (tested them too):

Added Robust YAML (slava0135), Github Pull Requests (GitHub), and the Fluent (macabeus) extension to the recommendations.

And finally, fixed very few comments in fluent files made #like this rather than # like this that would show up as errors with the fluent extension.

Port of Goob-Station/Goob-Station#966 & Goob-Station/Goob-Station#1192 (both of which I am the author of)

Why / Balance

Technical details

Requirements

• I have read and am following the Pull Request and Changelog Guidelines.
• I have added media to this PR or it does not require an ingame showcase.

Breaking changes

Changelog

no cl no fun

[FairlySadPanda]

Not sure why you've smeared out the SynthWave 64 recommendation. Everyone needs their SDE to match their synthwave coding background music.

Poking @PJB3005 on this as this is an interesting idea but she and others here historically have not had a good relationship with Git Kraken:

I will say that I've personally had issues with the Red Hat plugin for YAML deciding to hate all declarations of !type, and Gitlens is a... shareware? demoware? plugin that encourages the user to pay for it. Robust LSP is also a community project.

This might be one of those things that's great to merge on loads of downstreams but might not be suitable for upstream.

Github Pull Requests is an extremely firm recommendation though; it makes working with PRs far easier and is the key reason to keep VSCode around for some SS14 work now that Rider is free.

[Aeshus]

Thanks for the PR!

You'll need to make a separate PR for all of your documentation changes.

On the topic of the PR, I don't think you should include gitlens and should probably use slava0135.robust-yaml instead of ertanic.robust-lsp.

The rest seems good though, thanks again!

[Piras314]

I drew over synthwave because I didn't add it to the recommendations for obvious reasons, and that's just a screenshot of my extensions scrolled nicely to a point that shows all the added recommendations.

Red Hat YAML I will remove, I forgot that I hate it.

Gitlens just genuinely makes VSCode's existing integration better. I haven't had to pay for it or anything like that.

[FairlySadPanda]

I'll agree Gitlens is an improvement but I just hesitate as it absolutely nags the user about its paid features. Above my contributor paygrade (of minus eleventy billion dollars) to decide on.

The config runners for things like release builds looks handy fwiw but it's a bit esoteric for most developers; this is probably one for a maint who works on the build process to read.

[Piras314]

I removed gitlens and changed from robust LSP to robust YAML

[FairlySadPanda]

For the best. Now if only someone could PR making the VS Code C# language engine faster for Robust work... it's embarrasingly slow compared to Rider.

[Piras314]

For the best. Now if only someone could PR making the VS Code C# language engine faster for Robust work

wyci

[Piras314]

The main reason for the config runners is just so devs can quickly for example run a tools config for mapping, or go onto release if they're dealing with some weird bugs that only happen on debug or release (which has happened...) or if they just want to test some stuff out in regular old release sandbox.