Release 0.9.0

[nobodywasishere]

This would not have been possible without the efforts of @devnote-dev and @tlkh40! Thank you!

This is a complete rewrite from scratch to provide a faster, more reliable, and more maintainable extension. It should have feature parity with v0.8.4. The only thing that hasn't been rewritten yet is the tasks support, and that can come in a future update (alongside built-in debugging support).

Bugfixes:

• Error executing Crystal plugin. spawn crystal ENOENT #102, Error executing Crystal plugin. spawn bash ENOENT in Windows #172
• fix: Use a separate task provider for shards #145 (thanks @refi64)
• Color change when adding return type to class method #157
• Auto-formatting issue with some keywords #158
• Hover feature does not work with Windows11 PC and v0.8.4 of the extension (Native Windows Crystal, not WSL) #176
• With compiler path set properly still get error upon opening first .cr file  #177
• Stop the LSP when the extension is shutting down, where previously it would just stay on / active

New Features:

• Ability to view and debug expanded source code from macros #4
• Add support for Jump to Definition  #42
• Crystal support in Markdown code blocks #56
• Max processes not respected #122 (there's only one instance of the compiler running at once now)
• make Crystal grammar compatible with TextMate #150 (thanks @WhereIsX)
• Add unused variable highlighting #155 (thanks @grkek)
• Add Crystal Specs to native Testing UI #163 (disabled by default for user-experience)
• Supporting mutiple main files (entry points) for a single project #175 (by using crystal tool dependencies to choose a target from a file)
• GitHub Codespaces support (as long as Crystal is installed)
• Show problems in ECR files

This has been tested on MacOS, Windows (native), Linux (Arch), and GitHub Codespaces. While there still may be issues, this is a definite improvement over the old code. I've personally been using this for the past few months on projects big and small and it has worked well.

By default, the problems runner, hover provider, and definitions provider are turned on. This may not be ideal for larger projects due to compile times and memory usage, so it is recommended to turn them off in the vscode settings. That can be done per-project by creating a .vscode/settings.json file with:

// .vscode/settings.json
{
  "crystal-lang.definitions": false,
  "crystal-lang.dependencies": false,
  "crystal-lang.hover": false,
  "crystal-lang.problems": false,
  "crystal-lang.spec-explorer": false,
}

Or if those features aren't desired, they can be turned off user-wide instead of just for a project/workspace.

Attached is a build of the current code for any additional testing:
crystal-lang-0.9.0-alpha.3.vsix.zip

[devnote-dev]

Thank you @nobodywasishere for your hard work! Hopefully I'll be able to contribute more in the coming weeks, but from what I can see, things seem to be working well! 🚀

[bcardiff]

Yay! So excited to see this changes. Thanks for all the work!