Add support for ignoring console logging levels

[dancrumb]

Users just add a pluginOptions object to the Raven object:

Raven.config(/*...*/).install().pluginOptions = {
    console: {
        ignoreLevels: ["info", "debug"] // just the facts, ma'am
    }
}

[mattrobenolt]

Just throwing this out there for discussion? Is it a bad idea to use just a magic global for this? Or is that not a great idea.

I'm imagining a general "logging config" or something like exists in other languages.

I also don't write JavaScript much, which is why I'm asking. This just looks and feels really sketchy and I'm not sure of the best practices.

[dancrumb]

Since Raven is designed to run in entirely unknown environments then I
think the number of globals should be limited to the absolute minimum.

While I see where you're coming from for with regard to a general logging
config, in the browser, your pretty much limited to console for out of
band logging (i.e. not writing to the document.

I think you're right that it's a little sketchy. We're relying on users
glomming a configuration object onto Raven. However, the plugins are a
little loosey goosey at the moment anyway: no documentation of specific
plugins or the general plugin framework.

I'd be happy to spend some time on that, but right now, I'm keen to just be
able to tweak the console reporting so that I don't get rate limited to
oblivion
On Aug 28, 2014 5:53 PM, "Matt Robenolt" [email protected] wrote:

Just throwing this out there for discussion? Is it a bad idea to use just
a magic global for this? Or is that not a great idea.

I'm imagining a general "logging config" or something like exists in other
languages.

I also don't write JavaScript much, which is why I'm asking. This just
looks and feels really sketchy and I'm not sure of the best practices.

—
Reply to this email directly or view it on GitHub
#251 (comment).

[mattrobenolt]

That's fair. I'd like to have more attention into plugins in general.

If this solves the immediate issue you have, I'm ok with it since it doesn't change anything in raven.js itself and is purely isolated to the console plugin which very few people (afaik) use.

I'd be very open to seeing a proposal for a new setup going forward.

[mattrobenolt]

@dancrumb One last thing, can you rebase and squash these commits? You now have 4 extraneous commits that'll get merged with this. :)

[mattrobenolt]

@dancrumb Just waiting on a rebase/squash here and it should be good to go.

[QuentinFchx]

ETA ? :)

[dancrumb]

I created #328 to replace this