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
Yep, just come across this one myself. The workaround is to change the file association/language mode of the file temporarily to ordinary HTML and then change it back to Django HTML once finished debugging. It would be great to keep the native debugging functionality with the file remaining as a Django HTML template for the syntax highlighting and debugging together.
The issue might be on the VS Code side though, so it would be worth pointing this out to that team in case they can add this file association as an acceptable file within its code.
Not sure if there were any changes related to this but I have just tried to debug the Django template for the first time and it works even if the file type is Django HTML
Django extension version v1.10.0
VSCode 1.73.1
I'm running Django in docker and attaching to it using debugpy with the following launch.json
"version": "0.2.0",
"configurations": [
{
"name": "Project debug",
"type": "python",
"request": "attach",
"pathMappings": [
{
"localRoot": "${workspaceFolder}/project", // location in development tree
"remoteRoot": "/src/project/project/" // location in docker container
}
],
"port": 3000,
"host": "localhost",
"django": true
}
]
}
When the extension is enabled, the ability to add breakpoints in django html templates is lost for VSCODE.
This is unfortunate as clearly the two functionalities together - django template syntax highlighting and debugging - would fit so well together.
The text was updated successfully, but these errors were encountered: