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
Dark doesn't have a great debugging experience right now.
We have no support for breakpoints and step-debugging, and runtime errors are often opaque.
Dark-classic had some almost-excellent debuggability through the use of our Traces, but those aren't yet accessible in dark-next.
Once the baseline editing experience has advanced a bit, we need to circle back here, starting with how Traces fit into the debugging experience.
The text was updated successfully, but these errors were encountered:
StachuDotNet
added
blocked
Can't be worked on or finished right now, because it's blocked
and removed
blocked
Can't be worked on or finished right now, because it's blocked
labels
Jan 22, 2024
StachuDotNet
added
later
Let's think about this later -- we have some higher-priority things to work through first
needs-review
I plan on going through each of the issues and clarifying them -- this is to mark remaining issues
labels
Feb 8, 2024
StachuDotNet
removed
the
needs-review
I plan on going through each of the issues and clarifying them -- this is to mark remaining issues
label
Feb 19, 2024
Dark doesn't have a great debugging experience right now.
We have no support for breakpoints and step-debugging, and runtime errors are often opaque.
Dark-classic had some almost-excellent debuggability through the use of our Traces, but those aren't yet accessible in dark-next.
Once the baseline editing experience has advanced a bit, we need to circle back here, starting with how Traces fit into the debugging experience.
The text was updated successfully, but these errors were encountered: