Fix example code; add support for jsonpath vs json check if "$" is present in the JSON response example #19
Conversation
…onpath" vs "json" and can be used when not all keys can be compared via "json" mode e.g. eTags, last modified date, dynamic URLs
…body example(s) code that would always use the fake Latin values
|
Hey @mishushakov, this fixes some logical errors in the previous example fix or param and request body examples. The current code always produces Latin fake values... Also an idea to switch to jsonpath va json checker if author adds "$" in the JSON response example. Otherwise I do not know how people deal with changing etags, dates, and URLs when comparing responses. Using captures did not work within the same call and would be even more complicated to derive from the Open API schema. Will this automatically be picked up by Gruesse von LA nach Berlin, war dort 9 Jahre vor meiner Zeit in LA 😉 |
|
looks like since 0.3.9 nothing has been published which explains why the main stepci tool was still generating fine.
|
markusthegeek
changed the title
No description provided.