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

feat: expose faiIfNoPactsFound on the VerifierOptions #411

Closed

Conversation

adamwitko
Copy link
Contributor

@adamwitko adamwitko commented Oct 14, 2022

This PR is to add in the ability for Providers to specify if they want to pass or fail when no pacts can be found to verify.

Fixes (pact-foundation/pact-js#941)

@adamwitko adamwitko force-pushed the add-no-fail-if-no-pacts branch 2 times, most recently from 308f092 to 135691f Compare October 14, 2022 15:40
@adamwitko
Copy link
Contributor Author

  • Look in to adding more tests as these changes feel quite underdocumented

@adamwitko adamwitko marked this pull request as ready for review October 14, 2022 15:47
@mefellows
Copy link
Member

Thanks @adamwitko. I've been off for a long weekend, will review this week - appreciate the PR.

Most of this work is just mapping arguments to the underlying process, where the real logic/behaviour exists. I'm less concerned about an integration test for this behaviour at this layer, but we could look to sure up the unit test coverage.

A lot of the mapping is enforced at the type (TS) level, but of course this doesn't guarantee behaviour/validation in JS land.

@mefellows
Copy link
Member

Closing this one and have pushed a small change to address comments - thanks Adam, if the build passes I'll merge and release.

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

Successfully merging this pull request may close these issues.

2 participants