JBEHAVE-1606 Handle dynamic table meta only at scenario execution level #85
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
uarlouski
force-pushed
the
JBEHAVE-1606
branch
from
a1ef440 to
263c66b
Compare
uarlouski
changed the title
uarlouski
force-pushed
the
JBEHAVE-1606
branch
from
263c66b to
5f45471
Compare
uarlouski
changed the title
|
valfirst
approved these changes
Nov 21, 2024
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.
Examples table meta should not be parsed along with scenario meta because unlike scenario meta, the table row is local to particular row being filtered which is unknown at the time of regex story parsing but at runtime, this logic is performed in PerformableTree where scenario parameters are checked for the meta in rows.