(\n <>\n I am going to render this doc string in a textarea:
\n \n \n )\n}}>\n \n\n```\n\nIn each case where you provide your own component, it will receive the same props as the default component, plus two more:\n\n- `styles` - class names for the default styling, so you can still apply these to your custom component if it makes sense\n- `DefaultRenderer` - the default React component, useful if you only want to provide your own rendering for certain cases, and otherwise fall back to the default rendering (don't forget to pass it the props)\n\n## Build / hack\n\nInstall dependencies\n\n npm install\n\nRun tests\n\n npm test\n\nInteractive development\n\n npm run storybook\n\n## Ideas\n\n### `ScenarioList` component\n\nA component that renders a list of scenarios (possibly from multiple files, filtered by e.g. tag). \n\nThis component could be used to render relevant scenarios in 3rd-party tools, such as \nJIRA, Confluence and various issue trackers that support plugins.\n\n### Link to JIRA\n\nConfigure with a regexp and url function, and tags will be rendered as JIRA issue links\n\n### Search\n\nSearch by tag, but also by text. Could use http://elasticlunr.com/\nor https://lunrjs.com/ - or it could simply perform filtering on an array of `GherkinDocument` messages.\n\n### Search results\n\nEach scenario displayed underneath each other, grouped by feature file. The feature description is \"collapsed\", \n(unless it contains the search term) but can be opened.\n\n### Filtering / sorting\n\n* by tag\n* by duration (find slow ones)\n* by status\n* by recency (update timestamp) - exclude old ones\n* by flickeriness\n\n### Tag search\n\n* Render a tag cloud for all tags\n * Size: count\n * Color: pass/fail/undefined\n \n### On-demand data\n\nFor large reports (especially with screenshots) it may be too heavy to store it all in the browser.\nThe GUI should request data for the current document on demand. The GUI should also be able to filter\nwhat kind of events it wants. For example, to render the initial screen.\n\n### Server / App\n\nIt should be easy to use. Just run the app (Electron). It will create a named pipe where\nit will listen. What's written here gets written straight to the React app (no websocket,\nit's in the same process). This app can be fairly small.\n\n### Rerun tests\n\nAdd a message to represent a config+cwd+env for a run, so the GUI can rerun it.\nThe config is essentially command line options. They can be modified in the gui.\nRerun on file change can also be set up. This just makes the whole DX simple.\n\n### Alerts\n\nThe app could use the OS to send screen messages (autotest like)\n\n","readmeFilename":"README.md"}