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
I've been developping package locally, for this example I cloned the CSV package and made some commits that I'd like to debug; and I've loaded them into my 'develop' environment:
When I currently hit 'debug file in new process' the debugger will complain that the current environment doesn't have the package included. I think I can avoid this issue by just loading my 'develop' environment instead which already has the package added.
now I'd like to load this environment when starting up the debugger, but by default the debugger load the 'v1.9' environment, which contains no breakpoints and so my debugger doesn't stop. So is there a way to define this via the 'launch.json' file? I could not find this in the current documentation
I figured out myself that I can just select the 'develop' environment using the button on the VScode taskbar. And then run the debugger. So I'll add this to the documentation lateron so that others don't have to figure this out again.
The text was updated successfully, but these errors were encountered:
Hi all,
I've been developping package locally, for this example I cloned the CSV package and made some commits that I'd like to debug; and I've loaded them into my 'develop' environment:
When I currently hit 'debug file in new process' the debugger will complain that the current environment doesn't have the package included. I think I can avoid this issue by just loading my 'develop' environment instead which already has the package added.
now I'd like to load this environment when starting up the debugger, but by default the debugger load the 'v1.9' environment, which contains no breakpoints and so my debugger doesn't stop. So is there a way to define this via the 'launch.json' file? I could not find this in the current documentation
I figured out myself that I can just select the 'develop' environment using the button on the VScode taskbar. And then run the debugger. So I'll add this to the documentation lateron so that others don't have to figure this out again.
The text was updated successfully, but these errors were encountered: