-
Notifications
You must be signed in to change notification settings - Fork 990
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Api-side context
isn't available to the VS Code debugger
#5373
Comments
context
isn't available to the VS Code debuggercontext
isn't available to the VS Code debugger
Workaround posted in the discord:
Link: https://discord.com/channels/679514959968993311/970282715343642694/970417178153213953 |
This looks interesting. I will look into this. |
I regret looking into this. |
@IThinkThatsKirby What path did you take, what did you learn or what roadblock did you hit? Debugging is, for me, sort of a black box. So, I would be interested to hear any thoughts you have had. Discord is just as good a place to talk, if you are willing to talk, and if you don't want to muddy up the topic here. |
@pantheredeye |
So far I believe this is not really an issue. |
I took a walk and bounced some ideas off my 2 year old. I think context is not going to show up as a global variable in VS Code's debugger. The way its created is more of a pointer to where its located and is defined from a return in a function that does not get run until context is referenced. So due to hoisting its referenced as a local variable when ever it is called. I will do a test to verify this hypothesis and report back my findings tomorrow after lunch. OK so ill be spending the next few days learning how to make frameworks in typescript. then do the experiment. |
I kant find any docs on HOW vscode debugger works, we need a debugger for the vscode debugger so we kan debug while we debug. I am 100% in the camp of its not actually global in the way JavaScript is run in the node or browser environment. |
The global context object that's available to services doesn't seem to show up in the VS Code debugger.
The text was updated successfully, but these errors were encountered: