Closed andrewryan1906 closed 2 years ago
It was closed and I was unable to open it, and I wasn't sure if adding a comment to a closed issue would cause it to be visible to you; I apologize if this is a breach of protocol.
No problem - it's completely fine to comment on closed issues.
If you are using a JetBrains editor (such as WebStorm, IntelliJ IDEA, PhpStorm, RubyMine or PyCharm), and your license expired after June 2019, Wallaby automatically uses the latest version available for your license. In your case, this means you have our latest JetBrains plugin version (v1.0.238
), but are using an older version of Wallaby's core runtime (v1.0.801
).
If you have reinstalled and version v1.0.801
is still being used, it means that your license has expired and so Wallaby has automatically downloaded/installed the last version supported by your license.
To use optional chaining with Wallaby, you may renew your license via our website (select to Claim your existing user discount), or else email us: hello@wallabyjs.com.
If you'd like to confirm the issue doesn't exist in the latest version prior to renewing your license, you may request a 15-day trial.
Hello,
This is a follow up to #2975. It was closed and I was unable to open it, and I wasn't sure if adding a comment to a closed issue would cause it to be visible to you; I apologize if this is a breach of protocol.
Your response @smcenlly was that I was using an old version of Wallaby; I'm using the latest version, 1.0.238. To confirm, I just reinstalled and re-downloaded Wallaby from here:
https://plugins.jetbrains.com/plugin/15742-wallaby
I also reset the cache. Same error. Diagnostics report says plugin version 1.0.238; but oddly now, the core version says 1.0.801 (not 802). Not sure what the difference is between the plugin and core version is, or how I can get a newer "core" version.
Diagnostics report:
Thanks, Andrew