Closed
Description
When debugging a web app that is producing cast errors at runtime, a user would expect that:
- Debugger gets triggered, displaying the error message and Dart stack/code
- Console prints meaningful info, or at least the same contents as Chrome dev tools console
What happens instead?
- Debugger doesn't get triggered
- Console prints only a subset of Chrome dev tools console (Screenshot 1)
- User has to look at Chrome's console output and make best guesses where the error lies in Dart code (Screenshot 2)
What steps will reproduce the problem?
- Checkout this branch (it is missing a typecast when parsing json)
- Activate Dart, pub get
- Debug example/swords_man/index.html
IDEA EAP 2018.2
Dart SDK 2.0.0-dev.60.0
build_runner: ^0.8.9
build_test: ^0.10.2
build_web_compilers: ^0.4.0+3
OSX, Chrome
Also reported in Jetbrains YouTrack as WEB-33172
Metadata
Metadata
Assignees
Labels
No labels