Open TimothyJones opened 3 years ago
Here's a short test:
echo '{ "description": "a test mesage", "content": { "name": "Mary" } }' > msg
cat msg | pact-message update --consumer=CONSUMER --pact-dir=. --provider=PROVIDER
Sounds good.
Why is your example in two steps instead of echo '{ "description": "a test mesage", "content": { "name": "Mary" } }' | pact-message update --consumer=CONSUMER --pact-dir=. --provider=PROVIDER
?
No specific reason, just what I happened to write
Pre issue-raising checklist
I have already (please mark the applicable with an
x
):Software versions
Request
Currently,
pact-message
expects the content JSON to be passed as a command line parameter:JSON in a command line param is difficult to quote correctly on windows (I haven't found a library that works for all cases yet).
It would be awesome if we could work around this by having the option to pass the content via standard in: