blaze-react icon indicating copy to clipboard operation
blaze-react copied to clipboard

Implement Bug Reporter example

Open asayers opened this issue 11 years ago • 0 comments

From @meiersi:

Another option would be to implement generic GUI-bug-reporting support in blaze-react. In its simplest form it would consist of one application transformer that works as follows.

  • The rendered application gets wrapped with a toolbar that allows to switch between running the app, reporting a bug, and browsing bugs.
  • When reporting a bug, the application is paused, and the user can fill out a form describing the problem.
  • Submitted bugs get stored in a backend DB. For demo purposes, it might work pretty well to submit the bug straight to a github project using the Github API. I'd suggest to use a particular tag to identify them and to embed the application state as JSON in the issue text.
  • When browsing bugs, we read the bug DB from github and allow the user to restore the application from the state stored in the issue.

This version would require to log-in with their github account. For more real-world production use cases, we'd probably want to add support for.

  • Bug triaging
  • Drawing on the App UI to support handwritten annotation.
  • Recording a limited set of actions that were applied before the bug-report was submitted.

Note also that we could easily extend the application state with data about the browser version and the current time, by just using another application transformer that adds this information.

asayers avatar Dec 09 '14 17:12 asayers