You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardexpand all lines: docs/changelog/index.rst
+13
Original file line number
Diff line number
Diff line change
@@ -1,6 +1,19 @@
1
1
Changelog
2
2
=========
3
3
4
+
1.1.16
5
+
~~~~~~
6
+
* Fixed a bug that was preventing stack frames from ``raven.js`` from being hidden correctly. See: https://github.com/getsentry/raven-js/pull/216
7
+
* Fixed an IE bug with the ``console`` plugin. See: https://github.com/getsentry/raven-js/issues/217
8
+
* Added support for ``chrome-extension://`` protocol in Chrome in stack traces.
9
+
* Added ``setExtraContext`` and ``setTagsContext``. See: https://github.com/getsentry/raven-js/pull/219
10
+
* Renamed ``setUser`` to ``setUserContext`` to match. ``setUser`` still exists, but will be deprecated in a future release.
11
+
* New ``backbone.js`` plugin. See: https://github.com/getsentry/raven-js/pull/220
12
+
* Added support for ``chrome://`` protocol in Firefox in stack traces. See: https://github.com/getsentry/raven-js/pull/225
13
+
* Ignore more garbage from IE cross origin errors. See: https://github.com/getsentry/raven-js/pull/224
14
+
* Added ``Raven.debug`` to prevent logging to ``console`` when ``false``. Defaults to ``true`` for backwards compatability. See: https://github.com/getsentry/raven-js/pull/229
15
+
* Prevent calling ``Raven.config()`` or ``Raven.install()`` twice. See: https://github.com/getsentry/raven-js/pull/233
16
+
4
17
1.1.15
5
18
~~~~~~
6
19
* Fix issues if a non-string were passed to ``Raven.captureMessage`` and non-Error objects were passed to ``Raven.captureException``.
If at any point, the user becomes unauthenticated, you can call ``Raven.setUser()`` with no arguments to remove their data. *This would only really be useful in a large web app where the user logs in/out without a page reload.*
66
+
If at any point, the user becomes unauthenticated, you can call ``Raven.setUserContext()`` with no arguments to remove their data. *This would only really be useful in a large web app where the user logs in/out without a page reload.*
67
67
68
68
Capturing a specific message
69
69
~~~~~~~~~~~~~~~~~~~~~~~~~~~~
@@ -89,6 +89,14 @@ Passing additional data
89
89
90
90
Raven.captureException(e, {extra: { foo:"bar" }})
91
91
92
+
You can also set context variables globally to be merged in with future exceptions with ``setExtraContext`` and ``setTagsContext``.
0 commit comments