Support for SpecFlow 2.2.0 #2
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
jguc
approved these changes
Apr 17, 2018
|
Thanks, one of my first open source contributions 👍 Would you update the nuget version? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
In techtalk/SpecFlow@7098c83, IBindingInstanceResolver was renamed to ITestObjectResolver. Unfortunately this is a breaking change made on a minor version and has broken SpecFlow.Autofac.
It was simply a rename and all the contracts are the same, so all I've done is update the package and reflect the renaming. Note that SpecFlow 2.2.0 now has a Newtonsoft.Json dependency.
Additionally, the old project name and assembly were renamed to SpecFlow.SimpleInjector.SpecFlowPlugin. Tested with my personal project.