fix(dap): register adapter and configurations at startup - #550
Merged
Merged
Conversation
- `require("dap").continue()` works without running `:FlutterRun` first; user-defined adapter/configurations are kept
- Dart sessions started outside flutter-tools get log output and reload/restart commands
- Default configurations set `cwd` to the project root
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Closes #475
dartadapter and default configurations when the plugin starts, sorequire("dap").continue()works before:FlutterRun/:FlutterDebug. An adapter or configurations the user already defined are left untouched;debugger.register_configurationsis still called.dap.listeners.on_session), so log output, DevTools/VM service and reload/restart work for them.cwdto the project root.