Closed
Description
Currently Raven expects to be configured once, and further configuration requires resubmitting the full config object + DSN.
Setting some config values after initial config can be useful in some cases. For example, tagging all events submitted by a logged-in user as such, which happens to be the use case I'm interested in. That looks like:
- Load and configure Raven
- Wait for user login status
- If user is logged in, do Raven.setUser (works already) and also set "tags" option (doesn't work already)
Here's how I implemented this in a fork - just as a simple setter: gawkermedia/raven-js@getsentry:master...master . If this is something you'd consider for inclusion in master, I can document it and send a PR.
Metadata
Metadata
Assignees
Labels
No labels