-
Notifications
You must be signed in to change notification settings - Fork 0
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
katateIDE.configureClasspath not found #1
Comments
I will look into it ASAP in the time being you can add this line to file "karateIDE.karateCli.classpath": "src/test/java:src/test/resources:target/classes:target/test-classes:${ext:karate-ide.jar}" Please note the expresion I'll look into this as son as posible Thanks for reporting this |
I can confirm that there is an issue activating the extension when the workspace does not contain any karate files (like karate-config.js, features...) If you open a workspace with features or create a new one, the command should be available I will release a version fixing this in the coming days Thanks again for finding this.. |
Ahhh... I hadn't started building anything, yet, I was just getting the environment set up. Once I created a very basic config file it worked. But yeah, perhaps it would be nice if setting the Classpath via the Command Palette worked even if there weren't any Karate files in the project. Thanks for the quick & very helpful response! |
I have release a fix for this issue... It would be helpful if you can leave a review or some stars on the extension marketplace page Thanks a lot |
Great! I just left a review :) |
Hi there.
I'm having the hardest time getting Karate working w/Visual Studio Code. I figured the easiest thing to do would be to use KarateIDE & this Jar, but after installing the two & trying to configure the Classpath via the Command Palette (View > Command Palette> KarateIDE: Configure Classpath) I'm getting the following error:
Do you have any idea what's going on here & how I can fix it?
BTW, this is on a Mac.
The text was updated successfully, but these errors were encountered: