It would be remiss not to mention the extensions that have inspired this work, especially the Maintained Swift Development Environment. I’ve been using it for a couple of weeks now to work on some Vapor projects and it’s been great. Automatic generation of launch configurations for debugging with CoreLLDB.Error annotations and apply suggestions from errors.Jump to definition, peek definition, find all references, symbol search.It’s being guided by the SSWG but a huge shoutout goes to and who have done all of the work to get it ready for an initial release! One of the goals for 2021 for the SSWG was to improve the tooling for Swift on the server and this fills an important part of that. The extension aims to provide a first-class experience for developing Swift packages in VSCode. You can find the initial 0.1.0 release on the Visual Studio Marketplace here. I will probably give Rider and Visual Studio Mac a look to see whether they fare better on the above the points as I don't think VS Code will work for me.Here’s a Christmas present for those of you who prefer (or have to) develop Swift packages outside of Xcode - today we’re releasing the initial version of the VSCode Swift extension That plus the recent announcements that Unity will stop shipping MD with 2018 led me to try VS Code. Clearly some memory leak issues that were never addressed. Hated than MD crashed at least twice a day on OSX.I do like the code outline that displays in the right rail.The MD cmd+b first pass build was really nice for refactoring because it would immediately show you all issues in a search results window.
Probably there is a setting to turn this off but I don't see it.
code formatting/beautify is terrible on VSCode.Just switched from MonoDevelop to VS Code on OSX and here are my thoughts so far:
0 kommentar(er)
