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
global Dart variables are not currently shown in the debugger.
@nshahan did some investigation and found we will likely need to request the globals for the current library. In Chrome DevTools, they are discoverable in a closure with the library name:
The text was updated successfully, but these errors were encountered:
I'm anticipating there are some changes coming soon to the way DDC represents library global methods, getters, setters, and fields to support hot reload. This will likely need to be coordinated with dwds once we settle on a representation that works well. One idea is to use the same representation we use for class static methods, getters, setters, and fields so there might be an opportunity to reduce some of the logic required.
@nshahan just to confirm, supporting accessing globals from the debugger will have to wait until after hot reload support is added to avoid having to change the implementation?
It's not a hard requirement to wait, but I just thought it would help you prioritize this work if you know that it will likely need to be revisited in the near future when the runtime representation of library globals changes.
global
Dart variables are not currently shown in the debugger.@nshahan did some investigation and found we will likely need to request the
globals
for the current library. In Chrome DevTools, they are discoverable in a closure with the library name:The text was updated successfully, but these errors were encountered: