Hello, One of our provider send a JSON like ```{ ...
# general
é
Hello, One of our provider send a JSON like
Copy code
{
  "level": 0,
}
But suddenly, they changed the
level
value to
2
which broke our consumer. Is this something we should verify with a contract test?
m
m
An example of going from something like
{"level": 0}
to `{"level": "OFF"}`where you have a possibly unexpected different type due to a change stringifying an enum would be a valid use case, done that one before 🙂
é
The type is the same, but the value is inconsistent, it doesn't make sense to have
level: 2
on the first level of the object. IMHO that sound like Does the provider return the expected response? So we should enfore the value for this level
m
If you expect level 0 to be the response for a particular shaped request, then you need to ensure the provider always does so, you usually telegraph this via a provider state
if the
0
can be any number, then a
like
matcher is appropriate