For example, with a flutter proejct, everything is ok, but while running, it would run into panic like this:
This panic issue would only show when the App is under running. And it is easy to see that the debug stack information is quite a lot from the left debugging view--- Most of them are quite messy and not related to users code.
So I think it would be a quite useful feature for Copilot to gain the whole context of debugging and then give useful solution/advice then.
That is an interesting idea. I suppose here we could add a sparkle into the Exception zone widget, which on click would send the error as well as the stack trace potentially in order to fix the runtime error.
For example, with a flutter proejct, everything is ok, but while running, it would run into panic like this: This panic issue would only show when the App is under running. And it is easy to see that the debug stack information is quite a lot from the left debugging view--- Most of them are quite messy and not related to users code.
So I think it would be a quite useful feature for Copilot to gain the whole context of debugging and then give useful solution/advice then.