From fffc9ccdcc34bf9fe04fc5762097dd2cd6bd6f27 Mon Sep 17 00:00:00 2001 From: Matt Fellows <53900+mefellows@users.noreply.github.com> Date: Mon, 22 Jan 2024 09:32:38 +1100 Subject: [PATCH] docs: update how to override body data type --- consumer/junit/README.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/consumer/junit/README.md b/consumer/junit/README.md index 1948f41077..c23d8d559f 100644 --- a/consumer/junit/README.md +++ b/consumer/junit/README.md @@ -580,8 +580,8 @@ The `and` and `or` methods take a variable number of matchers (varargs). By default, bodies will be handled based on their content types. For binary contents, the bodies will be base64 encoded when written to the Pact file and then decoded again when the file is loaded. You can change this with -an override property: `pact.content_type.override..=text|binary|json`. For instance, setting -`pact.content_type.override.application.pdf=text` will treat PDF bodies as a text type and not encode/decode them. +an override property: `pact.content_type.override./=text|binary|json`. For instance, setting +`pact.content_type.override.application/pdf=text` will treat PDF bodies as a text type and not encode/decode them. ### Matching on paths