I suggest you ...

Provide a way to manually log warnings (console.warn)

Sometimes there are edge cases in code that don't trigger an exception, but you'd like to log as a warning with console.warn. It'd be nice to be able to see this in errorception.

26 votes
Vote
Sign in
(thinking…)
Sign in with: Facebook Google
Signed in as (Sign out)
You have left! (?) (thinking…)
Phil Freo shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →

4 comments

Sign in
(thinking…)
Sign in with: Facebook Google
Signed in as (Sign out)
Submitting...
  • AdminRakesh Pai (Founder, Errorception) commented  ·   ·  Flag as inappropriate

    Gregor, while that works just fine right now, I would lose the flexibility to make modifications to the API in the future if I need to. (To be clear, I don't foresee such a change right now, but I don't want to lose the ability to do so if need be.)

    Instead, I suggest you create errors manually and pass them _errs.push.

    Example:

    try {
    throw new Error(errorMessage);
    } catch(e) {
    _errs.push(e);
    }

    Documented in more detail here: https://errorception.com/api/client

    This isn't quite the same as logging console.* messages, so I'm leaving this issue open.

  • Gregor commented  ·   ·  Flag as inappropriate

    I dunno if that's meant to be that way, but I managed to send manual errors using

    _errs.push([errorMessage, location.href, -1])

  • Chris Greenwood commented  ·   ·  Flag as inappropriate

    Yes, especially for debugging on lot's of different devices and browsers it would be nice to be able to log some information for said edge cases.

Feedback and Knowledge Base