Always run onError callbacks for Chain.capture() in the parent zone (#31)
Closes #30
diff --git a/CHANGELOG.md b/CHANGELOG.md
index 5e56d8d..abb5b0a 100644
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -1,3 +1,7 @@
+## 1.7.4
+
+* Always run `onError` callbacks for `Chain.capture()` in the parent zone.
+
## 1.7.3
* Fix broken links in the README.
diff --git a/lib/src/stack_zone_specification.dart b/lib/src/stack_zone_specification.dart
index 1cccd3a..924f2ef 100644
--- a/lib/src/stack_zone_specification.dart
+++ b/lib/src/stack_zone_specification.dart
@@ -138,7 +138,7 @@
// TODO(nweiz): Currently this copies a lot of logic from [runZoned]. Just
// allow [runBinary] to throw instead once issue 18134 is fixed.
try {
- return parent.runBinary(zone, _onError, error, stackChain);
+ return self.parent.runBinary(_onError, error, stackChain);
} catch (newError, newStackTrace) {
if (identical(newError, error)) {
return parent.handleUncaughtError(zone, error, stackChain);
diff --git a/pubspec.yaml b/pubspec.yaml
index 94054ec..3c25051 100644
--- a/pubspec.yaml
+++ b/pubspec.yaml
@@ -7,7 +7,7 @@
#
# When the major version is upgraded, you *must* update that version constraint
# in pub to stay in sync with this.
-version: 1.7.4-dev
+version: 1.7.4
author: "Dart Team <misc@dartlang.org>"
homepage: https://github.com/dart-lang/stack_trace
description: A package for manipulating stack traces and printing them readably.
