Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Question: providerStates allowed in any contract? #89

Open
scraymondjr opened this issue Jul 19, 2021 · 1 comment
Open

Question: providerStates allowed in any contract? #89

scraymondjr opened this issue Jul 19, 2021 · 1 comment

Comments

@scraymondjr
Copy link

The spec README seems to indicate that providerState will be updated to providerStates for all contracts here, but it seems that language implementations are only updating the field for Message contracts (example commit).

Should providerStates be available for Interaction and Message contracts or is it correct that provider states with multiple states with params is only supported for Message types?

@uglyog
Copy link
Member

uglyog commented Jul 21, 2021

providerState is used in older versions (V1, V2) of the pact files. Versions V3+ it is the plural form.

Message pacts only exist with V3 (V1 and V2 are HTTP only), so should always use the plural with multiple values. However, if the spec version is set to V2 for HTTP pacts, it must use the single form.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants