You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In fact configuration allows to setup any StepPatternParser implementation, and predefined one allows to customized the prefix:
returnnewMostUsefulConfiguration()
...
// use '%' instead of '$' to identify parameters
.useStepPatternParser(newRegexPrefixCapturingPatternParser("%"))
...
Currently the only implementation available is RegexPrefixCapturingPatternParser which accepts different prefix, according to this, a new option should be added in project preferences to define the prefix used within the whole project. If a more fine grained setting is required, preference should be added on a per editor basis, which won't be done for now.
This would be a temporary solution until the possibility to associate a dedicated Runner to a story is available.
Note for myself: The runner will be responsible for configuring the JBehave Embedder in such way it could be used by the plugin to analyse available classes and figure out all candidates steps. One mustn't forget that the plugin would probably not be working at JDT level but at class level: performance would probably be impacted...
Parameters are defined using the '%' prefix whereas the documentation indicates:
The text was updated successfully, but these errors were encountered: