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
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?
The text was updated successfully, but these errors were encountered:
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.
The spec README seems to indicate that
providerState
will be updated toproviderStates
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?
The text was updated successfully, but these errors were encountered: