diff --git a/spring-cloud-contract.html b/spring-cloud-contract.html index de6a9798d3..c744312e09 100644 --- a/spring-cloud-contract.html +++ b/spring-cloud-contract.html @@ -417,14 +417,80 @@ body.book #toc,body.book #preamble,body.book h1.sect0,body.book .sect1>h2{page-b .show-for-print{display:inherit!important}} +.hidden { + display: none; +} +.switch { + border-width: 1px 1px 0 1px; + border-style: solid; + border-color: #7a2518; + display: inline-block; +} + +.switch--item { + padding: 10px; + background-color: #ffffff; + color: #7a2518; + display: inline-block; + cursor: pointer; +} + +.switch--item.selected { + background-color: #7a2519; + color: #ffffff; +} + +
WireMock can read response bodies from files on the classpath or file
system. In that case you will see in the JSON DSL that the response
has a "bodyFileName" instead of a (literal) "body". The files are
-resolved relative to a root directory src/test/resources/files by
+resolved relative to a root directory src/test/resources/__files by
default. To customize this location you can set the files attribute
in the @AutoConfigureWireMock annotation to the location of the
-parent directory (i.e. the place where files is a
+parent directory (i.e. the place __files is a
subdirectory). You can use Spring resource notation to refer to
file:… or classpath:… locations (but generic URLs are not
supported). A list of values can be given and WireMock will resolve