The best situation is to provide fixed values but sometimes you need to reference a request in your response. In order to do this you can profit from the fromRequest() method that allows you to reference a bunch of elements from the HTTP request. You can use the following options:
- `fromRequest().url()` - return the request URL
- `fromRequest().query(String key)` - return the first query parameter with a given name
- `fromRequest().query(String key, int index)` - return the nth query parameter with a given name
- `fromRequest().header(String key)` - return the first header with a given name
- `fromRequest().header(String key, int index)` - return the nth header with a given name
- `fromRequest().body()` - return the full request body
- `fromRequest().body(String jsonPath)` - return the element from the request that matches the JSON Path
fixes#237
without this change the local repository maven setup is completely ignored
with this change whatever you have set up locally will be taken into consideration
without this it can be misunderstood that execute() can be used with Strings
with this we're informing the users that the value of the given property (url, header, body) has to be uniquely a execute command
fixes#231
without this change we are not doing a deep copy of a collection thus we're accidentaly removing the original value
with this change we ensure that a deep copy is made
fixes#229
without this change the Gradle plugin works only by chance since the stub creation task is setting the proper paths. If you execute the task manually it will fail
fixes#222
when one provides .. in the path it's actually a collection. So if regex is there now we support it. If it's size check - exception will be thrown
fixes#217
with this change we no longer call the integer assertions on the size. We have our own custom size assertions.
Also we can do a flattened size assertion. If in the jsonpath there is [*] we can finally check the whole size and assert it properly
related to #217
