|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
- [jbehave-dev] [jira] (JBEHAVE-876) Wrong color... Volodymyr Sobotovych (JIRA)
- [jbehave-dev] [jira] (JBEHAVE-876) Wrong ... Alexander Lehmann (JIRA)
- [jbehave-dev] [jira] (JBEHAVE-876) Wrong ... Volodymyr Sobotovych (JIRA)
- [jbehave-dev] [jira] (JBEHAVE-876) Wrong ... Mauro Talevi (JIRA)
- [jbehave-dev] [jira] (JBEHAVE-876) Wrong ... Volodymyr Sobotovych (JIRA)
- [jbehave-dev] [jira] (JBEHAVE-876) Wrong ... Mauro Talevi (JIRA)

I'm thinking of using RegexStepMatcher to "mark" the parameters as it knows the structure of the step. For that matter I introduced the new interface method StepMatcher.markParameters and implemented it for RegexStepMatcher. You can find the sketch implementation in my private branch: https://github.com/wheleph/jbehave-core/commit/ebf77903883f5fdf4b9c0e441455ddd1eec3e71c
I think that introducing of the new interface method is OK because StepMatcher is not directly used in Configuration and hence there's a very tiny chance that it has been customized by someone whose code could be broken by that new method that should be implemented.
I think that we could also push marking of "examples" parameters (for ex. "Given Airline <air_code> is valid").
What do you think about that?