Deliberate and explicit usage of error properties about osu-ahr HOT 4 CLOSED

I am frustrated that javascript can throw objects that are not errors.
I always got tired of thinking about it and did it in a perfunctory way.

If you would be willing to write a PR I would welcome it.

from osu-ahr.

It may be redundant to include Error in our message since log4js shows ERROR.

logger.error(`${e.message}\n${e.stack}`);

[ERROR]: Couldn't eat the fruit, apple was rotten
// long error stack

from osu-ahr.

It may be redundant to include Error in our message since log4js shows ERROR.

In that case, it was indeed redundant, that was an example just in case there was a string like for another example:

  logger.error(`@Class#Method\n${e.message}\n${e.stack}`);

[ERROR]: @Class#Method
Couldn't eat the fruit, apple was rotten
// long error stack

or maybe, another considerable way without \n after the string.
I think the first way is much more readable than this second one below speaking of the output.

  logger.error(`@Class#Method ${e.message}\n${e.stack}`);

[ERROR]: @Class#Method Couldn't eat the fruit, apple was rotten
// long error stack

from osu-ahr.

Oh, I am sorry that I took it wrong. I just wrote what came to mind.

@Class#Method would be a useful keyword when searching.
I like the pattern where the first line contains only metadata.
logger.error(@Class#Method\n${e.message}\n${e.stack});

It will be difficult to sort out the error messages, as I have written them in an inconsistent manner.
If you can't handle it, let me know.

from osu-ahr.