Fix Java8StepDefinition.isDefinedAt #1255
Merged
Conversation
This file contains hidden or 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
|
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Summary
Fixes Java8StepDefinition.isDefinedAt as reported in #1254.
Details
While replacing ConstantPoolTypeIntrospector with TypeResolver in 657ce3a the creation of the Java8StepDefinition was moved from the JavaBackend to the generated step definition.
This removed one stack element between the invocation of the Lambda (e.g.
Given(....)) and the creation of the Java8StepDefinition.How Has This Been Tested?
Extracted LambdaGlueRegistry to make a unit test possible.
Types of changes