You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Adding test and example for recording and retrieving a complete response body (#7)
- adding explicit test
- extending README
<!-- Please describe your pull request here. -->
## References
- TODO
<!-- References to relevant GitHub issues and pull requests, esp.
upstream and downstream changes -->
## Submitter checklist
- [ ] The PR request is well described and justified, including the body
and the references
- [ ] The PR title represents the desired changelog entry
- [ ] The repository's code style is followed (see the contributing
guide)
- [ ] Test coverage that demonstrates that the change works as expected
- [ ] For new features, there's necessary documentation in this pull
request or in a subsequent PR to
[wiremock.org](https://github.com/wiremock/wiremock.org)
<!--
Put an `x` into the [ ] to show you have filled the information.
The template comes from
https://github.com/wiremock/.github/blob/main/.github/pull_request_template.md
You can override it by creating .github/pull_request_template.md in your
own repository
-->
@@ -310,6 +330,8 @@ The handler has two parameters:
310
330
-`context`: has to match the context data was registered with
311
331
-`property`: the property of the state context to retrieve, so e.g. `firstName`
312
332
333
+
To retrieve a full body, use: `{{{state context=request.pathSegments.[1] property='fullBody'}}}` .
334
+
313
335
### Error handling
314
336
315
337
Missing Helper properties as well as unknown context properties are reported as error. Wiremock renders them in the field, itself, so there won't be an
0 commit comments