Details
Improvement
Resolved
Major
Description
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.
Meta storyMeta = story.asMeta("story_"); Meta scenarioMeta = scenario.asMeta("scenario_");
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.
Activity
Mauro Talevi
made changes -
| Field | Original Value | New Value |
|---|---|---|
| Description |
On the back of 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-set meta properties, but can also be set to an empty string. |
On the back of 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. |
Mauro Talevi
made changes -
| Status | Open [ 1 ] | Resolved [ 5 ] |
| Resolution | Fixed [ 1 ] |
