New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Frustrating debugger UX #15635
Comments
Removed this from the 1.6 milestone. |
Removed Oldschool-Milestone-1.6 label. |
Added Editor-Debugging label. |
cc @scheglov. |
I think it is AssumedStale now. cc @devoncarew. |
Added this to the 1.7 milestone. |
Our debugging experience is leaving me very unimpressed. So, having modified my program enough to have a breakpoint I can then inspect the library (because we don't have any way of just seeing all the things that are in scope, so I can't evaluate, say searchIndex.map.containsKey(link.text) because there's nothing that can see both link and searchIndex).
If I type searchIndex.map then the editor freezes for 1 minute while it creates the huge toString. I'd really like to have more control over whether and by how much these things are truncated. So it's too big, and I'd like to reduce it, so I want to evaluate
searchIndex.map.keys.where((x) => x.startsWith("unittest"))
and it tells me it's a syntax error.
Alan Knight
////////////////////////////////////////////////////////////////////////////////////
Editor: 1.1.0.edge_031110 (2013-12-12)
OS: Mac OS X - x86_64 (10.9)
JVM: 1.6.0_65
projects: 6
open dart files: 56
auto-run pub: false
localhost resolves to: 127.0.0.1
mem max/total/free: 1983 / 502 / 180 MB
thread count: 33
index: 1202498 relationships in 212763 keys in 949 sources
SDK installed: true
Dartium installed: true
The text was updated successfully, but these errors were encountered: