Decision Table implicit conversion #210
Closed
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.
Hi Eric,
I noticed that in the following spec using a decision table, the name of the example method appears in the output when the decision table is converted to a spec part implicitly. It doesn't when I explicitly invoke ".form" on the table.
So with this pull request, I changed the implicit conversion from the table to a spec part to behave identically to the conversion from a form to a spec part. I'm not entirely sure what was/is going on, maybe an "auto example" was triggered by some kind of "example wrapped in example" kind of thing?
If this was indeed the expected behaviour, please ignore this pull request. :) But if so, you should probably document it somewhere. (The user guide on decision tables suffers from this behaviour, too, btw.)
Hope this helps anyway.
Kind regards
Andreas