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: Add new branch consumerVersionSelector options to verifier #343

Merged
merged 1 commit into from
Oct 29, 2021
Merged

feat: Add new branch consumerVersionSelector options to verifier #343

merged 1 commit into from
Oct 29, 2021

Conversation

adamwitko
Copy link
Contributor

@adamwitko adamwitko commented Oct 27, 2021

This implements the pact-js-core side of issue pact-foundation/pact-js#757


expect(
warnSpy.calledWith(
"Using the tag 'latest' is not recommended and probably does not do what you intended."
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm unsure about having the tests rely on the exact logger output, but I can't think of a nicer way to do this - and I do like that the warning is tested.

Copy link
Contributor Author

@adamwitko adamwitko Oct 28, 2021

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Normally I'd agree with you. Testing log output gives me the shudders. I thought that given the "latest" tag behaviour gives output to the consumers that is quite key, then it may be worth doing something minor like this :)

@TimothyJones TimothyJones marked this pull request as ready for review October 28, 2021 06:23
@TimothyJones
Copy link
Contributor

This is excellent, thank you so much!

I'm happy to merge this, but haven't because it was marked as draft (I'm not sure if you just meant "draft until someone reviews")

If you have the time, it would be excellent to get this ported into the pact-node branch too (having two packages in the same repo is an unfortunate side effect of some choices that were made while working on pact-js v10).

@TimothyJones
Copy link
Contributor

I've approved the tests, but they currently fail on PR runs due to a git issue - so don't worry when that happens.

@adamwitko
Copy link
Contributor Author

@TimothyJones

If you have the time, it would be excellent to get this ported into the pact-node branch too (having two packages in the same repo is an unfortunate side effect of some choices that were made while working on pact-js v10).

How is the pact-node branch being managed compared to the others? Is it a standalone branch where commits are merged in and it's being maintained separately to master? If so, should I branch off pact-node, pluck my changes , and raise a PR targeting it. Job done?

@TimothyJones
Copy link
Contributor

Yes, that’s exactly right. There are a few breaking changes so it’s hard to cherry pick across. I think in pact-node this is just a typescript type change.

We intended it to be short lived, but that wasn’t the way things worked out with the uplift to the rust core

@TimothyJones TimothyJones merged commit b7b5ca7 into pact-foundation:master Oct 29, 2021
@adamwitko adamwitko deleted the feat/issue-757 branch October 29, 2021 07:14
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