Skip to content

Mention tags as a valid option for Raven.config #194

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Mar 26, 2014

Conversation

mgedmin
Copy link
Contributor

@mgedmin mgedmin commented Mar 26, 2014

I looked for a way to specify unchanging tags (such as git commit hash of my software), and mistakenly decided it wasn't possible to pass them to Raven.config() because the documentation enumerated various possible options but didn't mention tags.

Bugs like #75 convinced me that this was supposed to be a supported feature. So here's a doc patch to avoid sending other users into confusion.

I looked for a way to specify unchanging tags (such as git commit hash of my software), and mistakenly decided it wasn't possible to pass them to Raven.config() because the documentation enumerated various possible options but didn't mention `tags`.

Bugs like getsentry#75 convinced me that this was supposed to be a supported feature.  So here's a doc patch to avoid sending other users into confusion.
@mattrobenolt
Copy link
Contributor

Ah. I have it documented for sending tags with each event separately: http://raven-js.readthedocs.org/en/latest/usage/index.html#passing-additional-data

mattrobenolt added a commit that referenced this pull request Mar 26, 2014
Mention `tags` as a valid option for Raven.config
@mattrobenolt mattrobenolt merged commit cce3f41 into getsentry:master Mar 26, 2014
@mgedmin mgedmin deleted the patch-1 branch March 26, 2014 18:29
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants