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
In pact-js the v3 UUID matcher will accept an example argument, and I'd like the same in pact-go as well, as we have some use cases where the UUID we need to use in the request to the provider is a specific one.
I wondered if it was because I was using v2 matchers in Go vs v3 in JS, but definitely haven't seen a /v3/matchers module to use instead.
Actual behaviour
Currently the UUID matcher auto generates a random UUID in the example, with no option to provide a specific UUID unless you use a non-UUID matcher instead.
Steps to reproduce
Relatively self evident.
Relevent log files
Not required
The text was updated successfully, but these errors were encountered:
It should be noted, the current UUID matcher is just a regex (so you could just use a regex). I think the simplest option here is to create a new matcher UUIDv4(example string) that accepts an example, but uses the same regex.
Software versions
go env
Expected behaviour
In
pact-js
the v3 UUID matcher will accept an example argument, and I'd like the same inpact-go
as well, as we have some use cases where the UUID we need to use in the request to the provider is a specific one.I wondered if it was because I was using v2 matchers in Go vs v3 in JS, but definitely haven't seen a
/v3/matchers
module to use instead.Actual behaviour
Currently the UUID matcher auto generates a random UUID in the example, with no option to provide a specific UUID unless you use a non-UUID matcher instead.
Steps to reproduce
Relatively self evident.
Relevent log files
Not required
The text was updated successfully, but these errors were encountered: