[
https://jira.codehaus.org/browse/JBEHAVE-648?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mauro Talevi resolved JBEHAVE-648.
----------------------------------
Resolution: Fixed
> Expose story and scenario elements as Meta
> -------------------------------------------
>
> Key: JBEHAVE-648
> URL: https://jira.codehaus.org/browse/JBEHAVE-648
> Project: JBehave
> Issue Type: Improvement
> Components: Core
> Reporter: Mauro Talevi
> Assignee: Mauro Talevi
> Fix For: 3.5.4, 3.6
>
>
> On the back of JBEHAVE-625, it can be useful to expose story and scenario
> elements (only top-level ones and excluding the user-defined meta properties)
> as Meta, which can then be used for filtering or matching.
> This can be done as a decorator method on the Story and Scenario model
> classes, e.g.
> {code}
> Meta storyMeta = story.asMeta("story_");
> Meta scenarioMeta = scenario.asMeta("scenario_");
> {code}
> where the prefix can be used to provide a namespace to avoid conflicts with
> user-defined meta properties, but can also be set to an empty string.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email