Make decision table use last scriptTable class in scenarios #620
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
…ubclass, not script table. This removes the need to have a scenario table subclass just to use a different script table class from a decision table
amolenaar
added a commit
that referenced
this pull request
Feb 8, 2015
Make decision table use last scriptTable class in scenarios
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.
Previously when you had your own scriptTable subclass and you wanted a decisionTable calling a scenario to use that scriptTable subclass you had to define your own scenarioTable subclass.
With this change that is no longer needed. A 'standard' scenario called by a decisionTable will use the last-used scriptTable class for its children.