Add vscode debug configuration for running a simulated device #57
Conversation
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
Collaborator
|
If vscode users are going to find it useful and it doesn't add bloat for other users then i'm all for it. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Add vscode debug configuration for running a simulated device.
The configuration automatically detects all config files in
examples/ands03_configs/and and prompts the user to pick one (with filtering based on typed input) when they run the configuration. This does require an additional extension (documented inlaunch.json).The alternative, if we did not want the additional extension, is to manually maintain a list of possible configuration files, meaning when one is added, moved, or deleted we must remember to update
launch.json. This would otherwise provide the same user experience.Thoughts welcome.