Hello everyone, I have a question about provider states it may be a bit general but since we are implementing pact with pact-jvm I post it here. Please let me know if I should post it elsewhere. When we have a provider state on an interaction that is not implemented in the provider verifier, it will fall in the default case. As a result our server doesn't behave as expected and we might not know right away that it comes from our "dummy" provider state. This lead to some painful debugging. I understand it might not be easy to workaround but I wanted to have your take on this ? Thanks in advance

What is the question?

Sorry end of the week... I want to know if this is the expected behavior for the provider states? and if yes , why? I feel like we should get an Unimplemented provider state error or at least a warning

By default, it will throw an exception and fail the test. However, there are annotations and extensions that can change that behaviour.

Oh ok, actually I'm implementing pact in scala with pact4s (which uses pact-jvm under the hood) I thought the issue was from pact-jvm but apparently not. I'll look into pact4s again. Thanks for your answer