Refactor how stack trace formatting is configured
This makes the configuration zone-scoped rather than global to a worker.
Showing
- lib/src/backend/stack_trace_formatter.dart 75 additions, 0 deletionslib/src/backend/stack_trace_formatter.dart
- lib/src/frontend/format_stack_trace.dart 15 additions, 0 deletionslib/src/frontend/format_stack_trace.dart
- lib/src/frontend/stream_matcher.dart 2 additions, 2 deletionslib/src/frontend/stream_matcher.dart
- lib/src/frontend/test_chain.dart 0 additions, 52 deletionslib/src/frontend/test_chain.dart
- lib/src/frontend/throws_matcher.dart 3 additions, 2 deletionslib/src/frontend/throws_matcher.dart
- lib/src/runner/remote_listener.dart 74 additions, 69 deletionslib/src/runner/remote_listener.dart
lib/src/backend/stack_trace_formatter.dart
0 → 100644
lib/src/frontend/format_stack_trace.dart
0 → 100644
lib/src/frontend/test_chain.dart
deleted
100644 → 0
Please register or sign in to comment