From 295abf9679b3a65e5bb2fcf37d9096d7743080e2 Mon Sep 17 00:00:00 2001 From: Marius Gedminas Date: Wed, 26 Mar 2014 15:12:28 +0200 Subject: [PATCH] Mention `tags` as a valid option for Raven.config 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 https://github.com/getsentry/raven-js/issues/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. --- docs/config/index.rst | 11 +++++++++++ 1 file changed, 11 insertions(+) diff --git a/docs/config/index.rst b/docs/config/index.rst index afc10c34d7cb..95738efcdc86 100644 --- a/docs/config/index.rst +++ b/docs/config/index.rst @@ -37,6 +37,17 @@ The name of the logger used by Sentry. Default: ``javascript`` .. _config-whitelist-urls: +tags +---- + +Additional `tags `__ to assign to each event. + +.. code-block:: javascript + + { + tags: {git_commit: 'c0deb10c4'} + } + whitelistUrls -------------