Skip to content

v19.0.1

Latest
Latest
Compare
Choose a tag to compare
@joshuataylor joshuataylor released this 20 Aug 16:04
v19.0.1
b698fda
This commit was created on github.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Learn about vigilant mode.

v19.0.1

Massive thank you to the community for your patience and kindness.

Please see Roadmap for the Project, and new Maintainer for the Plugin #3598 for more information about the roadmap -- we've got lots coming up!

Warning

As JetBrains has made changes to how plugins should operate on the main thread, a lot of functionalities may sometimes seem not to work, such as adding an SDK. This error is usually Slow operations are prohibited on EDT.
This is being addressed by moving slow code from the Event Dispatch Thread (EDT) to background threads. Threading Model.

Important

The plugin has been submitted for approval, and should be available in the coming days. This notice will be removed upon approval.

Installation steps

Download the Elixir-19.0.1.zip file from below, under Assets.

Tip

Please refer to the Install plugin from disk JetBrains documentation for how to install plugins manually.

  1. Ensure your IDE is 2024.2 or above.
  2. Open Settings -> Plugins.
  3. Click the cog icon and select Install Plugin from Disk.

image

  1. Select where the plugin .zip was downloaded and install it.
  2. Ensure the plugin is version 19.0.1.
  3. Click OK to close the plugin window and reload the IDE.

Enhancements

  • #3639 - @joshuataylor

    • Support JetBrains Exception Analyzer

  • #3640 - @joshuataylor

    • Bump intellij platform gradle to 2.0.1 and IdeaVIM to 2.16.0

  • #3643 - @joshuataylor

    • Fix RubyMine freezing for umbrella projects but showing the new project wizard as a temporary workaround.

JetBrains Exception Analyzer

This release is a patch release to introduce reporting errors via JetBrains Exception Analyzer.

This allows users to submit errors/exceptions by clicking on the red report icon when an exception occurs - previously this was handled by submitting errors to GitHub as issues.

This process is entirely opt-in, and exceptions/stacktraces must be submitted manually by the user. This will always be the case, where anything you submit will be opt-in - privacy is the primary concern for anything related to error reporting.

This process is now handled via JetBrains, all data is sent to them. Stacktraces contain plugin specific errors, and should not contain your code. You can verify this when submitting - you'll see what is being sent.

Issues will be manually created when a new error is submitted, and we'll try and get something hooked up to track the amount of reports for an issue, to show publicly how many times the issue was reported by users.

I humbly ask that where possible you do submit exceptions, as it helps prioritise and understand how often certain errors are experienced.

Bonus points for creating an issue with how to reproduce (if it doesn't already exist), as this really helps too! ❤️

Here is what you'll see:
SCR-20240820-toij

And what we see (the stacktrace, via the UI):
image

Assets 3
Loading