Open TJSteel opened 4 years ago
I've had a thought
When the user gets an error, it's currently dumped to the console, I think we should add an array to the ErrorHandlerService, and upon getting an error, we also add the error to the array.
This would mean that when the user comes to report a bug, they can attach a list of console logs they've previously generated which would help a lot in troubleshooting front end issues (currently we only see errors in the db when an error is passed back from the back end)
now that we have this issue list in a public repository, ORM may not need much more doing to it other than maybe providing a link to this repo,
It could still be useful to have an option to send error report though which will forward the previous error messages received to the server for further analysis in the case where the issue is only on the front end and not already logged by the server.
I propose that we create a section for reporting bugs, and new ideas
this could work in a similar way to the messaging in the stewarding process regarding replies / closing off suggestions / bugs
complexity high only because a db schema will also be required, as well as front and back end development