You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We don't yet support completion in the Debug Console, but there are various bugs/quirks that make it awkward to use. Implementing completion would be of more value if these issues were addressed.
14
14
15
15
16
16
## Unable to copy/paste with Cmd+C and Cmd+V in embedded DevTools windows on macOS
When multiple isolates are used, some isolates incorrectly show "Paused on Entry" in the UI even though they were only temporarily paused at entry while breakpoints were configured.
26
26
27
27
28
28
## Allow Grouping of edits in Fix All in Workspace by default
An upcoming feature "Fix All in Workspace" allows previewing changes before applying them. Dart provides groups for these edits but by default VS Code does not show them unless you use the context menu to enable grouping. It would be better if we could tell VS Code to group by default.
32
32
33
33
34
34
## Support pre-ticking edits when previewing Fix All in Workspace
An upcoming feature "Fix All in Workspace" allows previewing changes before applying them. By default, VS Code has all changes unticked and requires manually ticking each branch. It would be better if we could tell VS Code to pre-tick all changes.
Currently when selecting an existing file as a target for the "Move to File" refactor, VS Code shows a prompt "Do you want to replace it?". This is misleading because the file is not replaced, the items being moved are simply merged into it. Having a better API would allow this prompt to be avoided.
Editor Insets allow inserting content between lines in the editor. This might allow improved DartDoc previews, for example showing images and/or videos directly in the editor that are included in the markdown content.
49
49
50
50
51
51
## A separate TODOs pane to keep TODO comments out of the Problems list
Currently, TODO comments show up in the Problems list because there's nowhere else to show them. In projects with lots of TODOs (perhaps from other developers) this makes the Problems list hard to use. The only option is to disable TODOs (`"dart.showTodos": false`). It would be better if they could be shown seperately instead.
Flutter's very detailed dartdocs can often result in hovers obscuring the code you're trying to read. Being able to doc the documentation for hovers/code completion would avoid this.
It should be possible to use `(` to complete function calls and automatically insert parens but currently this does not play nicely with inserting argument placeholders.
97
97
98
98
99
99
## Allow Prominent Progress Notifications from Debug Adapters
Using the editor color picker currently converts any named Flutter colors to RGB values. Being able to provide a palette of colors to the color picker would make it easier to stick to a define theme of named colors.
This would allow improved formatting of diagnostic message ([for example lint examples](https://github.com/Dart-Code/Dart-Code/issues/3841#issuecomment-1048677129)).
A lack of guidance about the use of `detail`/`documentation` makes it difficult to provide [syntax-highlighted details](https://github.com/Dart-Code/Dart-Code/issues/2792) on code completion items.
VS Code's code folding currently only suports hiding entire lines, meaning closing braces disappear inside the fold instead of showing as `void method { ... }`.
139
139
140
140
141
141
## Support Searching "ClassName.fieldName" in Workspace Symbols
Searching for `ClassName.fieldName` does not currently work because VS Code only searches the final `label` (`"fieldName"`) and not the `containerName` (`"className"`).
145
145
146
146
147
147
## Show "package:foo/foo.dart" in Editor Tab Labels
0 commit comments