Skip to content

Feature Request: Allow setting (some) options after initial Raven.config call #213

Closed
@bregenspan

Description

@bregenspan

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:

  1. Load and configure Raven
  2. Wait for user login status
  3. 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

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions