Jesse strategy break point debugging in vscode. #3
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.
As a developer I'd be nowhere without breakpoint debugging, and I wanted to bring the other people I'm collaborating with up to speed on developing software so they needed this capability to learn how to write python. I'm using vscode to develop with Jesse. So I've forked the project-template and updated it to work automatically with vscode which means it will provide the user prompts to install docker, open in a container, etc. It also gives them a single button press to start debugging the code. It will work for both docker (in linux and windows) and with the jesse app natively in windows and linux.
Note: https://code.visualstudio.com/docs/containers/docker-compose
"In Python projects, you have the Dockerfile, .dockerignore, docker-compose*.yml files all in the root folder of the workspace. When you add another app or service, move the Dockerfile into the app's folder."