Danny Tuppeny
Danny Tuppeny
Changes in 74fd1ff0b6968cd59d3a03d2472897c25de482de broke an internal workflow because targets that start with `//` would not compute a first-path-segment and would skip the code that forces the debugger type to Flutter....
Using the code at https://github.com/DanTup/devtools/tree/bad-structured-errors, running the sidebar results in this error that appears to be missing information:  Specifically, it says "The relevant error-causing widget was:" but has nothing...
Because we mark breakpoints as unverified initially now, and we delete/re-create them when anything changes (because VS Code just gives us a whole new set), there's a noticable flicker. https://github.com/Dart-Code/Dart-Code/assets/21116742/daa2f555-2830-4fd7-8f21-7b00d4dc103c
We only need it for shell scripts (which is generally just `flutter`, but we should review all call sites). See https://github.com/Dart-Code/Dart-Code/issues/5017 This may reduce the chances of leaving orphaned processes...
This might be because Flutter was slowly activating in the bug, but I got this prompt even though I'm in a Flutter workspace (and using a Dart SDK from Flutter)....
While investigating #4436, I noticed this odd highlighting:  ``` ==> { "jsonrpc": "2.0", "id": 213, "method": "textDocument/documentHighlight", "params": { "textDocument": { "uri": "file:///Users/danny/Dev/TestStuff/dart-code-metrics/lib/src/analyzers/lint_analyzer/rules/rules_factory.dart" }, "position": { "line": 167,...
It's difficult to do this before the work is in the server (and available without copies of _fe_shared etc.), but we should have a test that verified macros are working...
There are a number of lints that were disabled during the TSLint -> ESLint migration that never got re-enabled, for ex: https://github.com/Dart-Code/Dart-Code/blob/c18efb17ecfc721768b7a0aa0310535dcfd5d16b/.eslintrc.js#L194-L200 One of these (no-floating-promises) would've caught an issue...
Currently the work done for https://github.com/Dart-Code/Dart-Code/issues/4604 is Windows-only. We need to evaluate options for adding to PATH on macOS. The original plan was to add symlinks to something like `/usr/bin`,...