2013/9/18 Mohamed Ashraf mohamed.ashraf.213@gmail.com:
On Wed, Sep 18, 2013 at 6:37 PM, Rouslan Placella rouslan@placella.com wrote:
On 09/17/2013 10:30 PM, Mohamed Ashraf wrote:
I use a line counts file to allow for some line number translation for submission of bug reports and the script that generates this file is run from the release scripts. If however a developer uses a git revision instead of a release, this file will not have been created. another situation is that the developer generates the file but does changes to the js files which renders the file obsolete.
I can detect the obsolescence of the file by checking of modification dates however what do I do if the file does not exist or is obsolete. should I disable error reporting entirely or just display a warning? keeping in mind that a problem with line number translation may result in inaccuracies of grouping similar reports together on the error report server.
if I am to entirely disable or display a warning, what should the message say?
I would go with disabling the functionality. If someone is using a pma version from git, they are probably techy enough to submit a report by hand.
Bye, Rouslan
should I even display a message that an uncaught error has occurred or should I ignore error reporting completely on git checkouts.
It makes sense to display a message that something went wrong.