-
Notifications
You must be signed in to change notification settings - Fork 54
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
The parameter givenConfigFileName cannot be passed through the public functions createStub(...) #1375
Comments
Hi @crcaguilerapo , Apologies for the late response. Thanks for sharing your concern. I will check this and get back to you ASAP. Thanks, |
Hi @crcaguilerapo , Thanks for your patience. There is an existing supported way to specify the configuration file path when working programmatically. While the Please refer the documentation for more details Please let me know if this help. Thanks, |
Hello @pranavgawri, Thank you! You are right, this worked very well for me in the contract tests,
but when setting up the virtual server of Specmatic to perform integration tests, it didn't work.
Do you know what could be wrong? Thank you, |
@crcaguilerapo Thanks for the details, we will check on the Virtual Service side. |
Hi @crcaguilerapo, can you try the same thing with the latest Specmatic version (2.3.0)? This seems to have resolved now. |
Hi @yogeshnikam671 , I'm using the latest versions I see on
|
Hello @crcaguilerapo , thanks for sharing the details. Please refer to https://mvnrepository.com/artifact/io.specmatic/specmatic-core Regards |
specmatic/core/src/main/kotlin/io/specmatic/stub/api.kt
Line 127 in 1e9c236
I think it's important to be able to pass the Specmatic configuration path for cases when it is stored in a different location than the root of the Java project.
At the moment, that attribute is inaccessible to developers.
The text was updated successfully, but these errors were encountered: