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
Hi,
I noticed that all contracts generated by the adapter seem to presume that we need an exact match only. I guess for bi-directional contracts it doesn't really matter as provider never executes consumer contact.
However, I'm trying to use this plugin for consumer contracts due to lack of the Graphql support with bi-directional contracts. In that case it would be great to be able to use like matchers especially for response.
Is it possible?
The text was updated successfully, but these errors were encountered:
My plan was to use it for req/res body.
I'm wondering would it be even possible with current code? As far as I understand code it uses cypress.intercept function and injects AFTER while cypress_adapter did the reverse. Which gave it opportunity to inject extractPayload call into the flow before passing it to cypress.
Hi,
I noticed that all contracts generated by the adapter seem to presume that we need an exact match only. I guess for bi-directional contracts it doesn't really matter as provider never executes consumer contact.
However, I'm trying to use this plugin for consumer contracts due to lack of the Graphql support with bi-directional contracts. In that case it would be great to be able to use like matchers especially for response.
Is it possible?
The text was updated successfully, but these errors were encountered: