Picks one template when several could render the page
All 2 scenarios hold
Pebble templates render a report, and a project can supply its own. Point the reporter at a template directory. The reporter then uses the files in that directory in place of the built-in templates, or on top of them.
The rules below read a report of one test class named Calendar. That class holds one table named Leap years, with the columns Year and Leap? and one row, 2004 and Yes. A report that small lets a rule state a whole page.
A directory can hold more than one candidate for the same page. The reporter settles on one, and it settles the same way every run. A report therefore never changes because somebody added a file beside another.
The alphabetical part carries no meaning of its own. It makes the choice the same every time. Do not design around that order. A directory that holds two templates for one page is usually a mistake, and not a decision.
| Scenario | Your template directory | Table page? |
|---|---|---|
| Two names that both match the page |
|
|
| The page's own name beside a match |
|
|