Details
Description
Currently @UsingPaths is using one fixed instance of StoryFinder class.
In order to use a custom StoryFinder class with the annotation, I would like to include an optional storyFinder element in the @UsingPaths annotation.
Activity

Field | Original Value | New Value |
---|---|---|
Assignee | Mauro Talevi [ maurotalevi ] |

Summary | Add an optional StoryFinder class parameter to @UsingPaths annotation | Add an optional StoryFinder class element to @UsingPaths annotation |
Issue Type | New Feature [ 2 ] | Improvement [ 4 ] |
Description |
Currently @UsingPaths is using one fixed instance of StoryFinder class.
In order to use a custom StoryFinder class with the annotation, I would like to include an optional storyFinderClass parameter in the @UsingPaths annotation. |
Currently @UsingPaths is using one fixed instance of StoryFinder class.
In order to use a custom StoryFinder class with the annotation, I would like to include an optional storyFinder element in the @UsingPaths annotation. |

Status | Open [ 1 ] | In Progress [ 3 ] |

Status | In Progress [ 3 ] | Resolved [ 5 ] |
Resolution | Fixed [ 1 ] |

Resolution | Fixed [ 1 ] | |
Status | Resolved [ 5 ] | Reopened [ 4 ] |

Status | Reopened [ 4 ] | Resolved [ 5 ] |
Resolution | Fixed [ 1 ] |
Since we are informing the path and the StoryFinder class in the @UsingPaths, we need a runStoriesAsPaths() method without parameter in Embedder class.
Or perhaps a new Embedder abstract class that already implements the run() method of Embeddable interface.