-
Notifications
You must be signed in to change notification settings - Fork 179
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Incompatible with 2022.2.1 #996
Comments
Thanks for the report @DmitriyZaitsev! I don't usually release builds for canary as they tend to move in build versions quite often, making it hard to keep up. |
@raniejade that's true about canaries, you're right! Wherein, I'm not reporting the issue related to the canary build. The plugin does not support 2022.2.1 at all. Moreover, I tried to install the plugin for the official IDEA CE 2022.1.2, but it doesn't work either. Summing up, I kindly ask for support for 2022.1.2 and 2022.2.1. I love this project and I've been using it for five years maybe. Thank you for making this possible. I understand you don't have time for maintaining this repo. I'd love to help in any way I can, but I don't have experience developing IDE plugins. I could make a relevant pull request if you tell me where to look and where to dig. I would be interested in figuring this out. Thanks! |
@DmitriyZaitsev ohh right. There should be a build in the dev channel if you would like to try: https://plugins.jetbrains.com/plugin/10915-spek-framework/versions/dev. I haven't done a release yet which should include support for 2022.* (I'll see if I have time this coming weekend). |
Hi @raniejade |
Hey @DmitriyZaitsev not yet unfortunately - have you tried the dev build of the plugin? (You have to download it and install it manually) |
@raniejade I have.
|
Since https://plugins.jetbrains.com/plugin/10915-spek-framework/versions/dev/176742 works fine with 2022.2, is it possible to officially release the latest version of the plugin? |
Hey @raniejade - upon upgrading to Android Studio Eletric Eel (2022.1.1) released last week, we're noticing that the latest Spek Framework plugin version isn't appearing in the plugin Marketplace and still marked incompatible. Any plans (or PR assistance required) to support AS 2022.1.1? |
I held back to the last, but, unfortunately, after five years of using this framework as the main and personally beloved, the time has come to abandon it in favor of Kotest due to the lack of tooling support. |
Is this Repo dead? I'm also facing issues with not being able to use the Spek plugin on the latest version of Android Studio |
Hey @hhariri I just remembered a time on an episode of the Talking Kotlin podcast that you mentioned starting Spek. Just to check my memory, I peeked at the contributors graph and it confirmed as much! I know you haven't been part of the project for a while now but as a godfather of sorts for the project I thought I'd try to see if you could weigh in. For the past 2 years The Spek Framework IntelliJ plugin has been slow to keep pace with IntelliJ updates. According to @raniejade the plugin needs some manual intervention by a maintainer to be compatible with new IntelliJ versions as they come out but there haven't been any maintainers able to do this for some time. I can tell from the several GitHub issues that many people still like Spek but are having problems with tooling support. I feel it would be tragic if the project withered away primarily because the IntelliJ plugin needs minimal compatibility updates. Is there any chance you could help get things back on track? Or put out a call for a new maintainer? Or should the project just be archived and some migration recommendations be made for users, as @DmitriyZaitsev has done? |
Hi @raniejade
I get the message
Incompatible: requires IDE build 213.* or earlier
on the Android Studio Electric Eel | 2022.2.1 Canary 5 #AI-221.4165.146.2211.8713749, built on June 17, 2022.Yet, I have to stay on Android Studio Electric Eel | 2022.1.1 Canary 3 #AI-213.7172.25.2211.8624637, built on May 21, 2022.
When will you have a chance to support the new version? Thanks!
The text was updated successfully, but these errors were encountered: