Let me bring Run and Debug output with me

Options
Connor McCormick
Connor McCormick Member ✭
in ? Request a feature
[image.png]If I click on the custom function `table_archive` I'll lose all my debug information. This makes debugging inconvenient. 

Bonus points if I could somehow click the debug statements and be teleported to the function it refers to
· Share on Twitter

Comments

  • Chris Coleman
    Chris Coleman Administrator

    ADMIN
    Options
    I'm honestly right there with you on this one. Being able to look back at my debug information as much as I want until I run again would be super useful. Passing this one along right away.
    · Share on Twitter
  • Sam Bevis
    Sam Bevis Member ✭
    Options
    Totally agree. The fact that you cant "copy" the debugging (with all the nexsted info) is also frustrating. I can copy the result into VS code and have it on another screen so I can work with it, but the Debug variables are much more handy.
    · Share on Twitter
  • Sean Montgomery
    Sean Montgomery Administrator

    ADMIN
    Options
     you are able to copy the result of each statement. We added that last week.

    https://mrkr.io/s/62ae3fc662f2140167edb1b2/0
    · Share on Twitter
  • Connor McCormick
    Connor McCormick Member ✭
    Options
     I think they mean copy the entire chain of debug info, not just one result
    · Share on Twitter
  • Sean Montgomery
    Sean Montgomery Administrator

    ADMIN
    Options
     ah gotcha... makes sense. Happy to add that in the next release.
    · Share on Twitter
  • Sam Bevis
    Sam Bevis Member ✭
    Options
     yes sorry I should have been more specific - when working with the function stack you lose all the run & debug info so I am constantly running/debug, find something, then click on function stack and lose the run an debug info... ideally if i could copy the entire run & debug i could paste into an IDE to refer to when interrogating my function stack 🙂
    · Share on Twitter
  • Connor McCormick
    Connor McCormick Member ✭
    Options
     Ideally ideally you don't even have to copy it to a separate place. It will just stick around in a referenceable way until you're done with it.

    Copying it to an external IDE is just a workaround anyway, right?
    · Share on Twitter
  • Sam Bevis
    Sam Bevis Member ✭
    Options
     the only other way I could see it happening natively would be to have the ability to "pop-out" the debug into a new window, as you need the screen real estate to continue to modify the function stack.

    A tool such as VS Code is great for debugging invalid JSON, etc, as it colour coded and you can hide nested objects for a cleaner appearance. One of the bugs/errors I always come across is arrays within arrays which can be hard to spot in Xano.
    · Share on Twitter

Categories